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.

show comments
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.

show comments
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.

show comments
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.

show comments
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.

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

show comments
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.

show comments
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.

show comments
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.

kaffekaka

I've heard words from colleagues to the effect that us devs should not be involved in projects until all the requirements are done, and that we should not come with proposals and pushback. "We should just build the dumb client."

It seems insane to me. I want to be even more involved in architecture, design and strategy now that AI speeds up the typing part. I can't understand their reasoning.

show comments
wasabinator

This whole promotion stance is nonsense. Nobody is getting promoted, they are getting devalued. More for less will be what happens. Technologists are probably the biggest lemmings when it comes to security of their own labour. Now that they are all talking about software factories it's the end game for not being needed.

MomsAVoxell

I wouldn’t say we promoted developers into architects - its more that we exposed developers who are poor analysts, requiring that they do more architecture to cover their asses.

teekert

Every dev has a bit of an architect in them, you have to. But non-devs probably don't.

I feel that, indeed I'm fast-tracking into the architect role (already started with some courses years ago but started my own company and went back to dev + sys-admin, arguably that latter is also a bit if an architect role), but the big models are also reasonable architects! Opus or Mistral Large 4, will often come with pretty smart suggestions on preventing cases like the one from tfa. Not always and when I am architecting webapps with databases with "complex" datamodels, the LLMs really help with the big picture view, steered by me (meaning I'm often struggling with walls of text explaining pros and cons of decisions), and I don't write any of the code anymore. It just makes edits in 5 places for things I want. I am the gate before comitting, I do stakeholder management, but I rarely find anything weird in proposed code. Usually I only push back when it wants extra dependencies I feel we don't need.

And the whole thing is so rapidly improving, the view in tfa is useful, but maybe outdated in a couple of months?

Oarch

I straddle construction and SWE and briefly struggled with this title. Both developers and architects have wholly different meanings!

JKCalhoun

I found that over my 40+ years as a programmer, I became an architect after having worked with several dozen API over the years and having written (and maintained) several dozen apps and frameworks over that time.

It does seem to me that had I been vibe-coding this whole time, it is unlikely I would have improved as an architect.

show comments
spacebear

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

show comments
silver92bullet

My biggest question is how are we going to pass down the tricks of performance to juniors if they are overly reliant on the AI. It seems like this would be a good spot for mentorship to help a junior engineer build intuition and pick out when the AI is wrong and a better design.

hoppp

Yes. I have been an architect all along, but I needed to write the code. Now that coding is solved I can fully devote my attention to architecture.

stuaxo

I've always had to do some of the things mentioned.

On the other hand... there are jobs out there that are proper SW architect job, how does one even transition from dev to architect - is it even a thing a dev wants to do ?

Is it something where you really need a mentor ?

ramesh31

I'm just tired. This job used to be so cozy. Take your time to think deeply about a problem, and fully understand the solution. Now it's just an inch deep on 20 things at once, while being responsible for doing the job of what used to be a whole team. I know most of us are just lucky to still be employed at this point, but it's completely exhausting. If coding is no longer part of the job then why even bother anymore, and just become one of the people that talk and send emails for a living.

show comments
Blackarea

This example would fit for a junior engineer more than an architect where i come from

bengold14

Couldn't agree more except that these are architects that are actually implementing and need to deal with the pesky details of building. Engineer-Architects.

The problem is the abstraction we still expect them to use is code. In most companies architects didn't use code at all. We need a new abstraction that focuses on architecture.

(full disclosure I work in this space https://www.archme.io)

hosh

Roy Fielding and Christopher Alexander has quite a lot to say about architecture.

AI models already have their works in training data. I spend much of my time in conversations about architecture as a grammar — a pattern language, not just patterns

water42

This article is wrong; frontier models are absolutely good enough to realize blocking code is bad. Show me the prompts!

cluckindan

”AI … is also sycophantic and tries to execute your requirements exactly without pushing back”

In my experience, this is not true. Multiple times I’ve asked it to do things against guidelines and plans, and every time it has pushed back.

show comments
JackSlateur

These dev have been promoting themselves to job seeker without informing themselves.

smrtinsert

We were always architects. They just dont want to pay us for it.

bluefirebrand

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

show comments
sneak

Every programmer is and was a systems architect whether they knew it or not. Many are just bad at it, and still are.

Programming is a lot more than knowing syntax and APIs.

DeathArrow

>Why AI won’t push back

That's a false assumption. I got AI pushing back a lot of times. Maybe the author is not familiar with using AI? And you can, of course, instruct AI to be even more pushy.

>AI is great at writing code. But it doesn’t know if you are launching the app or have millions of users,

But it does know if you inform it.

Also, humans do not always push back. They either don't care or the pushback can be detrimental to their own goals.

DeathArrow

>Why AI won’t push back

That's a false assumption. I got AI pushing back a lot of times. Maybe the author is not familiar with using AI? And you can, of course, instruct AI to be even more pushy.

>AI is great at writing code. But it doesn’t know if you are launching the app or have millions of users,

But it does know if you inform it.

LeafItAlone

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

show comments
6thbit

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

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

show comments
lordnacho

If instead of becoming a software engineer, you became a civil engineer, you would not be pouring concrete and tightening steel cables.

Until very recently, a software engineer did the equivalent things: looking for small coding errors, hooking up libraries, writing unit tests.

Now, those things can be done by an LLM. All that is left for a software engineer is to do the actual understanding of architecture, and to be responsible.

Of course I can understand that people mourn being able to look over their implementation of some algorithm deep in the bowels of the product. That used to be fun. I can understand that young people in the field now face uncertainty, because doing the little things used to be how you paid your dues so that the seniors could explain to you how the big things were done.

It was like a deal, you would join the firm and do the stuff that was necessary, in exchange for training. You had time to learn the big things, because the little things took time.

There's another business that I started in where the gap also went away. In the old days, traders used to do their work on paper. There would be clerks who would note down trades, and check that the firm's positions were in fact what the senior trader thought. Pretty mundane stuff. But at the end of the day, you would sit with the boss and he would explain what had actually happened while you checked things.

I happened to land just as the transition was finishing: instead of taxing your physical conditioning by having you jog around the floor in a coloured jacket, the work went on a computer. The computer would let you solve the small things faster and better than you could ever do yourself. But it would also be the end of that guy who was just a good grinder. Now you had to use the machine to do new things in the market, and people started needing degrees to get the job in the first place.

The very nature of the entry-level job changed. The job itself opened up as well, though the fundamentals at a high level remained.

show comments
zug_zug

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 comments
jimnotgym

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

I'm afraid I can't let that one slide. Where do we start with this.

Is it more important than having a good product to sell, for instance?

Is it more important than maintaining your existing customers?

Is sounds so creepy to me, monitoring customers...

throe839384949

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!

gavinray

  > "Since logging was the first line to execute after installation, the welcome screen took 15 seconds to load."
Apparently written by a dev that never got the email that computers can do more than one thing, nowadays.

The logging could have taken 1,500 seconds and it wouldn't be a big deal if it had been punted off the main/UI thread...

hden

Nah. We demoted them to glorified crane operators without informing them.

t43562

I'm sorry what's the point of all of this? Just keep prompting until the slowness goes away. Don't get loaded with details. Architects shmarchitects because programmers shmogrammers! If it's slow then tell the fleet to swarm in and solve it!

martini333

Why is a LLM not concerned with performance again? Just tell it to be.

Animats

> 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 comments
giantg2

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 comments
mannyv

Don't forget, they've turned everyone into architects and QA people.

cush

AGENTS.md

This app has millions of users…

Solved.

croes

Promoted? So they get more money?

bill10

Or AI did

BatchJob

I refuse to reframe my worldview of software just because of some LLM sycofants comments.

jon128

From a cloud hosting provider perspective, the office of the CFO specifically, the vibe coding is great.

debo_

You asked developers to be adults without informing them

themgt

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.

show comments
j45

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

slj

As an aside from the contention of the article, while I don’t intend to enrage anyone here, could we please all refrain from the Generic He pronoun? Singular They has been a feature of English since the 1400s iirc, and to me using these it comes across as being intentionally pompous

show comments
gspr

"Promoted". Some people wanna do.

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

0c3ca83

Architect was long considered a bullshit job for the out of touch.

6510

into astronauts

viklove

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

tschellenbach

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

show comments
solyin

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

Love that attitude!