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.
hinkley 10 minutes ago [-]
I would say that I expect senior engineers to have autonomy, and autonomy means not doing strictly what you are told. So if you’re not being told exactly what to do, that means you have to figure it out for yourself. Which leads to stearing task direction, which leads to pushback on requirements.
And that’s why junior engineers are fucked at companies that can afford to send all their proprietary information to Anthropic. But since they are public now, they will violate that trust as soon as major shareholders learn to word it so that it sounds like a stranded asset that any responsible C Corp would be expected to rescue. And then everybody’s fucked.
rsyring 22 minutes ago [-]
I run a development firm so we've had all kinds of clients and interacted with various external dev teams over the last 20+ years.
You aren't an outlier exactly, but there are way more devs than you are probably aware who are just told what to build and then have to go build it. So they don't have or never developed the consulting, planning, and architecture skills and experience.
The more our clients tend towards wanting a process like that, and the less they treat us like valued expert software consultants that can help shape their solution for the better, the worse the outcomes usually are.
CSSer 6 minutes ago [-]
I'm a self-taught woman who started work in agencies doing front-end work, then moving on to progressively more complex tasks, eventually becoming a lead and doing all of the things you mentioned. Your experience maps to mine 1:1. I've had a lot of imposter syndrome and challenges around this, and I had to go through a similar realization at some point in my career. It sort of sucks because I am just not good at being that kind of blinders-on developer. I also mention my sex/gender because I've had lots of borderline offensive assumptions made about me in certain situations related to what you've described.
hinkley 6 minutes ago [-]
We call those body shops. Probably because sweatshop sounds overwrought if you know what those are actually like.
uptrails 43 minutes ago [-]
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".
ihsw 5 minutes ago [-]
[dead]
pjmlp 48 minutes ago [-]
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.
bikeshaving 21 minutes ago [-]
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.
hinkley 3 minutes ago [-]
I can generally tell which PRs are AI on the OSS projects I do reviews for because the release notes are a Steinbeck novel instead of written as a one line description meant to be read among a litany of others. But then they sort of do that for everything don’t you think?
mellosouls 58 minutes ago [-]
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.
QueensGambit 48 minutes ago [-]
OP here. You may be right about architecture being wiped away in the future, but we have to ship with today's tools. Also, architecture is about tradeoffs and could have longer staying power:
> AI coding tools are tuned to implement your functional requirements and two non-functional requirements, i.e. security and backward compatibility to avoid breaking your app. This invariably leads to:
- Architecture that trades off performance for security and slows down the app.
- Multiple versions of datamodel design with redundant tables, columns and code.
bluefirebrand 7 minutes ago [-]
I don't view becoming an architect as a promotion :/
tschellenbach 38 minutes ago [-]
Actually, you should always hill climb security and performance. AI can optimize these things if you ask it to.
baq 33 minutes ago [-]
That’s just one prompt in a loop though.
6thbit 17 minutes ago [-]
Sorry but Nah. Architecture has always been a part of the job.
If you weren't doing it, you were doing it wrong.
zug_zug 47 minutes ago [-]
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]
htrp 35 minutes ago [-]
tell your director he can do it himself with AI.... and see how far he gets
throe839384949 7 minutes ago [-]
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!
Animats 35 minutes ago [-]
> 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?
docshock 23 minutes ago [-]
Sample size is king.
giantg2 40 minutes ago [-]
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.
Seattle3503 6 minutes ago [-]
In addition to that and reviewing other people's AI slop MRs, I've also been promoted to devops. So many promotions.
solyin 51 minutes ago [-]
> You got promoted. Nobody told you, so I am telling you.
Love that attitude!
viklove 1 hours ago [-]
> 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 19 minutes ago [-]
[dead]
Rendered at 19:42:18 GMT+0000 (Coordinated Universal Time) with Vercel.
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.
And that’s why junior engineers are fucked at companies that can afford to send all their proprietary information to Anthropic. But since they are public now, they will violate that trust as soon as major shareholders learn to word it so that it sounds like a stranded asset that any responsible C Corp would be expected to rescue. And then everybody’s fucked.
You aren't an outlier exactly, but there are way more devs than you are probably aware who are just told what to build and then have to go build it. So they don't have or never developed the consulting, planning, and architecture skills and experience.
The more our clients tend towards wanting a process like that, and the less they treat us like valued expert software consultants that can help shape their solution for the better, the worse the outcomes usually are.
Try that with photography, painting, or music: "AI music has promoted musicians to architects".
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.
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.
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.
> AI coding tools are tuned to implement your functional requirements and two non-functional requirements, i.e. security and backward compatibility to avoid breaking your app. This invariably leads to:
- Architecture that trades off performance for security and slows down the app.
- Multiple versions of datamodel design with redundant tables, columns and code.
If you weren't doing it, you were doing it wrong.
[and your director now is convinced all his stupid ideas are both brilliant and very safe]
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!
Priorities.
Useful question for "analytics" people. If you only collected data for every thousandth customer, would you have less useful insights?
Love that attitude!
Lol, sounds like something only a junior developer or intern would say.