logoalt Hacker News

We promoted developers into architects without informing them

111 points • by QueensGambit • today at 6:17 PM • 73 comments • view on HN

Comments

whycombinetor • today at 7:14 PM

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.

➕ show 5 replies
uptrails • today at 6:59 PM

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".

➕ show 3 replies
nixpulvis • today at 8:00 PM

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.

pjmlp • today at 6:54 PM

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.

➕ show 4 replies
mellosouls • today at 6:44 PM

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.

➕ show 2 replies
bikeshaving • today at 7:21 PM

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.

➕ show 1 reply
dhpe • today at 7:50 PM

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.

➕ show 2 replies
spacebear • today at 8:34 PM

A basic prompt like “is this code performant?” would probably catch this problem with current models.

LeafItAlone • today at 8:21 PM

> Since logging was the first line to execute after installation, the welcome screen took 15 seconds to load

If you go from a (presumably) reasonable load time to one of 15 seconds and it’s not caught before getting merged, you have bigger problems than developer vs. architect and AI coding.

The premise of the post has merit, but the example is a terrible choice.

6thbit • today at 7:24 PM

Sorry but Nah. Architecture has always been a part of the job.

If you weren't doing it, you were doing it wrong.

➕ show 1 reply
j45 • today at 7:53 PM

The role of developer is evolving, and it doesn't means developers scale into architects automatically. They get to learn, which is great.

zug_zug • today at 6:55 PM

Exactly. You are now PM, Architect, and QA but get paid the same salary

[and your director now is convinced all his stupid ideas are both brilliant and very safe]

➕ show 1 reply
Animats • today at 7:07 PM

> Monitoring new customers is the most important part of running a business...

Priorities.

Useful question for "analytics" people. If you only collected data for every thousandth customer, would you have less useful insights?

➕ show 2 replies
themgt • today at 8:34 PM

Yesterday, I was debugging a performance problem with our Google Forms addon. It turned out my colleague had vibe coded the logging part, so that he could monitor the new installs every week. ... All of these are one line of code, but internally each of these makes multiple API calls to Google servers. Since logging was the first line to execute after installation, the welcome screen took 15 seconds to load.

AI is great at writing code. But it doesn’t know if you are launching the app or have millions of users, which it needs to make the right architecture call to log a timestamp vs email. It is also sycophantic and tries to execute your requirements exactly without pushing back, which means you end up with a slow app that takes 15 seconds to load a static welcome screen.

It is so paranoid about security that it will never write code to accept an unauthenticated payload. Even if you write it yourself, it will rewrite it into an authenticated payload and screw up performance or force users to sign in again on your app.

Just incredible seeing this post at the top next to "Unforced Navier-Stokes singularity, and the Generalized Riemann Hypothesis". We're at the "Japanese soldier who kept fighting 29 years after WW2" stage of AI denialism.

throe839384949 • today at 7:35 PM

I think we should not promote existing developers!

If AI is even remotely capable, we should fire all staff, and hire the same number of people in Nigeria! Diverse workforce is by far the most important goal! And it reduces CO2 emissions from commuting! And we save money!

giantg2 • today at 7:02 PM

It seem I was not only "promoted" to architect but also to PM/BSA. I'm having to gather requirements straight from managers and end-users and document everything, in addition to developing and leading another developer under me. The really interesting part is that my new role (after being pushed out of a Dev role) isn't even in the development/architecture family of jobs. Fuck corporations.

➕ show 2 replies
bluefirebrand • today at 7:35 PM

I don't view becoming an architect as a promotion :/

➕ show 1 reply
gspr • today at 8:04 PM

"Promoted". Some people wanna do.

Jesus, this is gonna end up being middle managers all the way down. Get a grip!

viklove • today at 6:35 PM

> If you are a senior developer or architect who understands the number of API calls behind each method, you would have:

Lol, sounds like something only a junior developer or intern would say.

sick_of_slop • today at 7:23 PM

[dead]

tschellenbach • today at 7:04 PM

Actually, you should always hill climb security and performance. AI can optimize these things if you ask it to.

➕ show 2 replies
solyin • today at 6:50 PM

> You got promoted. Nobody told you, so I am telling you.

Love that attitude!