AI June 7, 2026 mixed ⇧ 359 pts across 3 threads

AI is repricing software engineering identity and skill

Three threads today circle the same uncomfortable question from different angles. The 'LLMs are eroding my software engineering career' post is the most direct signal: engineers are watching their leverage shrink and they are not sure what replaces it. The Harness post about shipping a million lines of code in weeks with Codex provoked a mix of awe and disgust, with commenters calling it 'half-baked CRUD' at industrial scale. The tokenomics paper asks whether the next generation of senior engineers will be people who optimize token consumption in agentic workflows rather than people who optimize algorithms.

The pattern here is not just about job losses. It is about what competence means. Google famously hired on systems-thinking and optimization. The tokenomics thread explicitly asks whether companies will soon hire on how well you can reduce the token cost of an AI workflow. That is a real shift in what expertise looks like, and it is happening faster than most engineers expected.

The counterpoint in the comments is real though: the Harness million-line codebase drew heavy skepticism. People noted that volume of AI-generated code is not the same as quality, and that someone still needs to understand what the code is doing. The debate is not settled, but the direction of travel is clear.


So what?

If you are hiring engineers right now, the question of what to optimize for is live and unresolved. Founders who build tooling or platforms for developers should pay attention to where leverage is actually shifting, because the engineers you hire in two years may have a fundamentally different skill profile than the ones you hire today. Betting on raw output volume as a metric is probably wrong; betting purely on the old craft signals may also be wrong.

Read these