Most people who are good at their job understand the greatest value comes from deep understanding and internalization. Some people have been in roles where alie

Most people who are good at their job understand the greatest value comes from deep understanding and internalization. Some people have been in roles where alienation from the code is institutionalized, and they've been playing that role for so long that the idea of having a strong understanding and near prescient mental map of a 2 million line codebase sounds absurd. I think the question is less about the capabilities of LLMs and their outputs (because obviously that can change), but because they represent a workflow which codifies exactly that role I mention. You fulfill the role of a manager more than a programmer. You have a vague idea of the codebase, but lack any kind of intuitive mechanical understanding. There are many cases in which I can see an issue, identify the problem, and have it fixed faster than you could prompt an LLM to investigate. After a certain point of familiarity, all reasoning is local reasoning. That's the power of mechanical sympathy. Many, many large shops don't give a shit. They've long since galloped into the dark woods of bureaucratic know-nothing hell. Let the LLM figure that shit out. Those shops are already optimizing for maximal output and churn, so the value proposition seems obvious. I've been smugly saying it for years, but LLMs have me saying it quite a lot more these days: "Sure looks like it sucks down there!"