AI Didn't Take Your Coding Job—It Quietly Made You an Architect
We promoted developers into architects without informing them
A Google Forms addon took 15 seconds to load a static welcome screen because AI-generated logging code made multiple API calls to fetch user emails and IDs. The author argues that AI coding tools, tuned for security and backward compatibility, won't push back on requirements or consider performance—so developers must now act as architects: defining data models, constraining AI, and reviewing its output. The promotion happened without anyone telling them.
Essentially, if you generate code by specifying your requirements instead of specifying your architecture, AI will decide the architecture on your behalf.
- whycombinetor
Am I an outlier in that every SWE job I've had has expected you to push back on requirements and design the data model for tickets you are handed? Even when the org was large to have an architect, they just were just a figurehead and designed the original system, and ongoing decisions were made by the dev who picks up the ticket.
From that perspective, engineers are still engineers, just without the hands-on-keyboard coding. If that's all your job was, hands-on-keyboard coding with no decision making, yeah you're cooked and need to reskill.
- nixpulvis
I strongly believe good software teams (very rare) require members to play many roles. Sometimes you're a PM, sometimes you're an architect, sometimes you're the systems engineer. Enough people have enough context on the bigger picture that it's stable and there's a shared vision.
More often than not, one person does the majority of this, and does their best to break up the responsibilities. A good CTO does that at the top, and it flows down through the ranks depending on how big the org is. Perhaps it's just a CTO and 5 engineers, perhaps it's a CTO with 5 divisions, each with 10 groups, with many teams.
Flatter structures of engaged members works best from what I've seen, but you need to have a critical mass of people not only willing to take initiative, but empowered by leadership.
- bikeshaving
I’ve found that the “job” of using AI is mainly foible management. What the author describes here is a habit of coding agents to excessively use and create logging infrastructure, and sloppily leave it in production code even when unnecessary. For instance, I created an IPA IME keyboard (https://ipabet.org/), and I found in review that Claude would leave the debugging tooling around unflagged, which essentially made the program a key-logger.
These foibles come and go: early Claude Code refused to let programs crash, mangled all the comments in your codebase, and then one week you find that it insists on ending all functions with `Of` as in `layoutOf()`, `viewOf()`. Finding and mitigating these annoying habits becomes part of the job. Code review becomes articulating with this entity why certain patterns in the code are silly and should be changed.
The author mentions performance and security issues as the domain of “the architect.” For performance, I’ve found that Claude Code has more or less solved this domain, and can profile and optimize code across a variety of stacks and languages using sophisticated, ad-hoc workflows. For security, it’s just an ever-ending nightmare where random habits and sloppy implementation create random vulernabilities, compounded by the fact that Anthropic has added “safeguard filters” whenever you naively say you’re looking for them. Nevertheless, I’m not sure the architecting role as they describe won’t be automated in the near future.
- ChrisMarshallNY
> But AI will never make that call for you, because it doesn’t know your users and it won’t push back on your requirements.
In my case, I have been able to mitigate this. I have an LLM (ChatGPT, but I don't think it matters that much, anymore), that I load with vast amounts of information about the end-users of my apps. It generally makes excellent decisions, and often pushes back on my requests, if they may not deliver a good result. I sometimes think it knows more about my users than I do. One example, is that it does a very good job on translation. The feedback has been overwhelmingly positive. It blows away the stuff I used to have done by professional translation agencies.
I still feel that I need to design the overall architecture, but I sometimes wonder if that's just because I'm a control freak.
- pjmlp
The problem is that usually each team only needs a single architect.
What is happening is no different when developers got promoted into team lead of the offshoring team.
Which also didn't require that many team leads onsite, and off they were, everyone else that wasn't leading any offshoring team.
- uptrails
No one is getting promoted. The most likely future is that your job will pay less and will be less fun, as you're increasingly just a "liability sink" for decisions made by an LLM.
Try that with photography, painting, or music: "AI music has promoted musicians to architects".
- t43562
Ideally architects have the cross team vision of how things should fit together. They should be developers and should be making the sort of plans that developers are too busy to make and be thinking out a bit further into the future. They should be a bit more generally knowledgeable about all the different products even if they're deeper in one.
Do you need them? Well if you have enough teams and you don't want them to do ridiculous things that clash... yes.
Are AI vibers architects? Well perhaps they're now dealing with areas they're not used to dealing with but does it really matter? Just keep prompting till the problems go away!
- mellosouls
A dev moving down to architecture is not a "promotion".
Architecture is no more immune to AI than software engineering.
OP is describing somebody using AI poorly, and seems not to have a great handle on the way all jobs are impacted and boundaries being wiped away.
- dhpe
It took me years to learn that an architect is a different job role than a developer. I always thought every developer must understand software architecture deeply to do their job. Later I discovered that there are architects who just draw diagrams. I was blown out.
- lerouxb
This is gatekeeping. Everywhere I've worked every candidate goes through systems design interviews and it is expected that every employee pushes back on and considers architecture and system design.
The market for dedicated architects has always been vanishingly small.