Thread

1. simonw · 1790612858 · focus · HN ↗

   If you don't understand how your system works, your ability to make good decisions about future work on that system quickly degrades.

   I don't think you need to review every line of code, but you absolutely do need to be able to describe how the system works and its high level structure.

   As is so often the case with coding agents, having experience as a tech lead or engineering manager really helps here. You are responsible for a large system that has been worked on by multiple different collaborator (both human and agentic). You need to be able to make smart, informed decisions about that system, and talk with credibility to other stakeholders about what it can and cannot do and sensible next steps for the project.

   1. curt15 · 1790613123 · focus · HN ↗

      What will the path to a tech lead look like when it's no longer paved by thousands of hours of experience internalizing code? How do future tech leads avoid becoming like people who never got comfortable with fractions because they offloaded all arithmetic to calculators from an early age?

      1. simonw · 1790614088 · focus · HN ↗

         My hope/hunch is that the kids will be alright. Not learning effectively is a choice: if you want to get good, the paths to getting good are all still available to you.

         We have never had as abundant a supply of tools to help us learn our craft. I expect that many people will thrive.

         People who are a bit lazy and prone to cheating will be able to hurt themselves even more.

Unofficial Hacker News client; not affiliated with Y Combinator.