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. verdverm · 1790613460 · focus · HN ↗

         I had agents deep diving OpenCode source over the weekend, writing research docs, and helping me with a set of plugins. I learned quite a bit from the process and markdown walls, enough so that in later sessions I was able to point the model at where it was conflating concepts and help narrow its search.

         Ai can help you learn if you are intentional about it.

Unofficial Hacker News client; not affiliated with Y Combinator.