Thanks for clarifying. There have always been technical leads and hands-on engineering managers, but two things have changed: 1. The balance of responsibilities attributed to different titles has varied over time and across different companies. 2. Early personal computers were so resource limited that there were only so many programs you could write that actually made effective use of large teams. Today we can write much larger programs, which requires more coordination (across people and with AI—which can reduce the number of people required).

I would also strongly push back on the assertions that being very technical means spending most of your time on the code, and that you have to be using AI all day for it to be useful. Let’s say I’m a technical lead or a manager reviewing a design doc for a large project. I have an idea based on my years of technical involvement for how to significantly improve the quality or delivery timeline for the project. I used to have to ask the doc author to look into this approach, not knowing for sure if it would directly translate. Now I can take my crazy idea, quickly dispatch a coding agent to try it out against the codebase, go to a meeting, and then check on what it came up with to give a much more informed and technically accurate suggestion on the doc. I still have to have the technical expertise to iterate a bit with the agent and not over or under state the possible impact of my idea. But this lets me take say an hour rather than a week to come up with a vetted recommendation that saves months on the schedule.

I'm just speculating why the current structure of companies is not maximizing what AI can offer. Until it becomes completely self-directed and reliable, using a tool that allows you to move fast requires more technical knowledge, not less. What you're missing from your example is releasing to production without breaking it, dealing with increasing complexity as more features are added, maintaining development pace as more features are added, and trying not to create more bugs than are fixed.

The idea is more or less benefiting from doing work in bulk which AI is now allowing. I even think multiple engineers (human redundancy to double check the same code) should team up with one AI system and form a small team that handles millions of lines of code, with the only job to feed incoming tickets and check the AI work. Anyone not reviewing code should be facilitating everything else with their own AIs. I think large companies can collapse entire engineering departments into a few people. The cost would be that everyone else has to think like an engineer to sort out requirements and provide direction, but as you point out, this is now easier with the help of AI.

Actually, there is one other important thing that has changed: as developing a certain amount of functionality has gotten easier with modern languages, tools, libraries and coding agents, it’s also gotten less interesting for technology-driven people and more accessible to career-driven people.

Implementing the first text edit field in your program is kind of interesting when all you have is asm and 4k of RAM. Nobody wants to bother doing it manually when you have a web browser that can eat gigs of RAM.