• Home
  • Technology
  • Gaming
  • Entertainment
  • World & Business
  • Science
  • Sports
  • AI
HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • HomeTechnologyGamingEntertainmentWorld & BusinessScienceSportsAI
    • Home
    • Technology
    • Gaming
    • Entertainment
    • World & Business
    • Science
    • Sports
    • AI
    AI
    Reaction

    Knowledge gaps in large codebases, with or without AI

    A developer says they were unfamiliar with one detail of how tagged skills attach to prompts passed to the Claude SDK. They argue that working with partial understanding is normal in engineering.

    T-
    1 Source, 6h ago, first seen 6h ago

    TLDR

    A developer pushes back on criticism of that knowledge gap, saying the codebase has over 300 contributors and millions of lines of code. They argue that no one knows every implementation detail in a codebase that size, regardless of AI use, and worry that treating such gaps as failures could hold junior engineers back.

    Combined views

    99.3K

    1 Source, first seen 6h ago

    Combined views

    99.3K

    1 Source, first seen 6h ago

    800 likes
    800 likes
    95 comments
    174 saves
    14 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Featured Source
    95 comments
    174 saves
    14 reposts

    Sentiment

    Positive——Negative

    Summary

    Not enough discussion yet.

    No sentiment analysis available yet.

    Today's Rank

    —

    Not ranked yet

    Today's Rank

    —

    Not ranked yet

    1 Source

    @theoAnother day of Unemployed Kyle (aka WDS) dunking on me because he has no real career experience. His main complaint here is that I show multiple instances where I didn't know the depth of how part of a codebase worked. Sounds bad until you realize it's a codebase with over 300 contributors and millions of lines of code. Doesn't matter how much AI is used, nobody knows the implementation details of all the code in a real world codebase like this. The example he highlights is one where I was unfamiliar with details of how tagged skills are attached when we pass prompts to the Claude SDK. Funny enough, I know a lot (probably too much) about how we tag skills and how messages are passed over SDK, but this one intricacy was new to me. Knowledge gaps like this are the norm in real world work. Learning to operate with partial understandings of systems is key to long term success as an engineer, regardless of AI usage. I'm genuinely scared that inexperienced devs like Kyle are going to trick well-meaning juniors into holding back their careers.

    1 Source

    @theoAnother day of Unemployed Kyle (aka WDS) dunking on me because he has no real career experience. His main complaint here is that I show multiple instances where I didn't know the depth of how part of a codebase worked. Sounds bad until you realize it's a codebase with over 300 contributors and millions of lines of code. Doesn't matter how much AI is used, nobody knows the implementation details of all the code in a real world codebase like this. The example he highlights is one where I was unfamiliar with details of how tagged skills are attached when we pass prompts to the Claude SDK. Funny enough, I know a lot (probably too much) about how we tag skills and how messages are passed over SDK, but this one intricacy was new to me. Knowledge gaps like this are the norm in real world work. Learning to operate with partial understandings of systems is key to long term success as an engineer, regardless of AI usage. I'm genuinely scared that inexperienced devs like Kyle are going to trick well-meaning juniors into holding back their careers.