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.
> 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?
Yes, that is how most functional organizations operate.
Architects are a bad meme, along the same lines as scrum masters and product managers.
Good software engineers spend more time on design than implementation, and the best are helping their teammates with design, and auditing designs of adjacent teams to ensure integration success.
So architecture is an important part of the job, but that doesn't mean that you can automatically declare a role with the title "architect" and make the whole organization better at design.
Architect roles are a bad meme because the architect always ends up knowing less about the system and how it is used than the engineers and support staff, yet they have more influence over the decisions affecting those things. That's the essence of an organizational anti-pattern/bad-meme any time it shows up: influence over resources anti-correlated with decision quality.
Additionally, architects often report to non-technical folks fairly high up the chain. Those people are bad at screening for such a technical role, sometimes even making the mistake of replacing an architect with an external hire.
Good architects delegate down and are there to ensure the big picture remains consistent while leaving the teams to sweat the details because they are closer to the problem.
Bad architects try to micromanage and those are the cases where you end up with systems that are slow and unworkable with processes that have too much ceremony.
When in that role I focus on supporting the team. Mentoring, resolving disagreements, providing broader context, suggesting more options to consider (often stuff we could copy from older systems), etc.
The main area where I spend influence on really shape the outcome is on process and team culture, not any specific technical decision.
AI still doesn't really teach anything on the org-dev level. Organizations that where dysfunctional in the past will keep growing these structures only that now the complexity will increase much much faster because teams can do (vibecode) so much more.
I've always treated the architect role as more setting broad goals, defining boundaries for individual ownership, and technical dispute resolution. Sort of what you see with a lot of directors of movies where you get the best work by empowering individuals to completely own a carefully built little box that is a brick in the larger work.
Those could be done by normal management, but I've found it better to separate those discussions from management style discussions. Sort of like how the BDFL role in a large open source project is rarely anyone's actual boss.
Albeit, I'm still recalibrating what all this means in an agentic world. It makes sense with the little swarm I directly command, but the pressures for downstream ICs to ignore the art and taste of what they're doing is more than a bit unfortunate since the core of what I'm saying is to empower them to give a shit and be proud about what they built.
> architect always ends up knowing less about the system
I guess that depends. In automotive, at least in my case, the SW architect on our team knows so much more about how our SW module interacts with the overall system, it's almost awe-inspiring. My guess is, they have all this knowledge because they're continuously interacting with other architects and teams to talk about the big picture.
A lot of organizations don't know how to hire and task architects appropriately. I had the same opinion until I worked in an org where they actually functioned the way you'd think they should. Then I saw the chief architect's name in a 20 year old commit. They had no idea how to hire new ones, but they'd figured out how to grow and task them, which is a good substitute.
> Architects are a bad meme, along the same lines as scrum masters and product managers. Good software engineers spend more time on design than implementation, and the best are helping their teammates
> Architects are a bad meme, along the same lines as scrum masters and product managers
I think it says a lot about our culture that, even though xore agile literature and practices like XP and DX have again and again shown what works, the IT world stubornly keeps gravitating towards taylorian structures.
> Architect roles are a bad meme because the architect always ends up knowing less about the system and how it is used than the engineers and support staff, yet they have more influence over the decisions affecting those things.
A good architect is IMHO someone who can get the bullshit out of your way. Think like interfaces with third parties (or even other departments at your average megacorp), it certainly doesn't hurt if someone else has both the awareness and the technical knowledge about dependencies I have or others have on me, and can take care of dealing with the associated bureaucracy.
(And no, that's not a PM role because most PMs can't tell JSON apart from XML...)
It took me several years to realize this wasn't the default. Once I was senior enough to start getting people under me, I would assign tickets like "Scientist Bob would like a better method to view missing data, work with him to develop that over the next 2 weeks", and assume that they, like me, would enjoy the flexibility and the ownership. I didn't care what they came up with; email notifications, enhancing the web tool we have, putting coverage data in our opensearch to query, etc.
After getting complaints, I started getting narrower and narrower in my ticket writing, until I realized many newer software engineers literally want tickets like "modify function x_y_z() in python_file.py so that it also returns..."
I think this is an underratedly common experience. What makes it such a whiplash is that you're probably both at the beginning of a rather steep learning curve, but only just realizing that learning curve even exists. And reluctant to consider the implications, because of the impact it would have on your existing world model.
For inexperienced engineers it's that "your job is figuring shit out, not typing the code in", which for some people is like telling them that their dream job doesn't exist/the mental model most of their peers operate under isn't true.
For a manager it's that you can't really assume that everybody has the same personality/relationship to work/experience as you do, and that you might have even forgotten what it was like to be in their position, or not noticed how different some of your colleagues were from you. Which is also like telling them, "it turns out the best manager for your team is not the one you would want for yourself, and this job is going to be very different from what you thought".
I think it's very important to have a large enough sample of non-reporting colleagues across the range of experience. It helps you passively form a model of what normal career and even just life development looks like, and when you're in situations like this where you're not sure whether you're the asshole, or the other person is, or just confused, you can kind of in retrospect see how the near-peer may have navigated the same thing.
Same goes for interacting with enough non-developers and business people/customers/higherups to get some about the purpose of your role. Your role is downstream of what you do for them.
The problem for me is other people’s code. I don’t know what they want or what they will approve so I can’t just give them a solution that they’ll disapprove of. Having enough rejections leads to “tell me what you want me to type so that you’ll approve the pull request”
Yeah. There are some teams I work with that are exactly like that, and it pisses me off. If I need to write the ticket in such detail then it would be faster for me to write the code myself.
In my experience, that is still a little shortsighted. If you actually end up giving up and "just do it yourself" then you can often end up spending lots time with a long tail of fallout this entails. Suddenly some tests failing, some other team unexpectedly getting disrupted by your change and having to follow up on that and dealing with them, some follow up requirements revealing themselves... It is all those things that you are only on the hook for once you actually do it that often makes it worthwhile to instead dump all your thoughts into the ticket and then let somebody else do the grunt work, LLM-assisted or not. And it should add some humbleness to the attitude you just expressed.
Yes this has been a long time irritation for me. By the time I spec the feature to the degree these juniors require, I could have just done it myself. When I try to raise the level they work at, they just fall back to asking me incessant dumb clarification questions, refusing to take any ownership. No matter how often I have coached them on what the expectations is.
And now, I'm trying to get them to understand that if they persist in just being basic coders, they are shortly going to be replaced with an LLM.
Woah, no designer, no BA, no PO, no SME, no legal? I'm envious.
Aside, I've been thinking of the "reverse Uncle Ben": With great responsibility comes great power. Or should come. I've seen places where ICs were expected to "own" the work, as you mentioned, except they had no autonomy to actually make decisions, those would come by committee or from above. No wonder people didn't want the responsibility.
Curious if this is a culture issue or a volume issue.
In the distant past of a couple of years ago, I saw and gave tickets with higher ambiguity and opportunity for ownership and cross-team collaboration. There was breathing room to take that kind of time.
This year, however, as we're all aware, the expectation around speed is much higher. When more spinning plates are added, I want them to be more defined so they can be handled quickly. To be clear, though, I much prefer the former scenario.
It's cultural from what I've seen. Especially where development time is micromanaged, story points mean minutes and hours and estimates are put under a microscope. In short, low trust environments where managers have never developed software and probably have no idea what is going on i.e. situationally unaware management.
Similar. As a PM I try to learn how much direction each person is cool with in this moment of the career. I don’t mind specific details if the person needs them, but I love it when the dev knows the domain, the problem space, etc and we talk about outcomes and capabilities then off they go, driving the momentum and making recommendations about scope reduction or additional features that I’d never have thought of in advance. Then I’m mostly breaking ties and figuring out the next important thing to build.
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 steering 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.
In 15 years of career, I have never seen or worked for a place that had only “coders” (people who were just typing code and not thinking or pushing back or giving their opinions about tech and product).
So whenever i hear that coders are out of job because of AI, I always wonder where were those “coders”. Never met one
This exists on certain large companies that rely on very cheap labor, ofter overseas contractors. You have 2 or 3 people who understand the system and are actually trying, and people who want to communicate via jira tickets, and care little about whether what they are doing helps the company in any way, or has wide repercussions. In those companies, a Claude agent is still cheaper, and more reliable.
At good firms that try to pay competitively, of course this doesn't happen much at all. But yes, it's unsettling to get to work, and have someone tell you that what they want is 3-4 well defined tickets that they'll write in the next two weeks, and don't want to engage even a little bit more.
That was the role Microsoft seemed to expect of me, back in 2008-2009. Here's the spec, go type in the code, the suitability of the design is not your concern.
I did not like that very much, and did not stay too long.
I've worked at one or two places that were like this, where I was expected to just do what the ticket said and not push back on anything. Thankfully, it's not too common, and most places I've been at seem to be pretty receptive of ideas traveling upward from individual developers to management.
Separately from that, pushing back is often uncomfortable and unrewarding. Even in places that do expect developers to have autonomy, it seems like there's usually some people that choose to just follow directions because it's easier and there's no consequences for doing so.
The belief is that prompting AI for some code gives you good architecture as well, because the AI magically knows what you aren't telling it. Or, maybe more generously, because a good vibe coder will give the AI a prompt that includes enough to derive what the architecture should look like.
If your use case is very ordinary it does work that way. It's only at the bleeding edge or in a weird edge case that performance or optimization stops being a problem you can solve by paying for a bigger box. The performance rarely matters for a SaaS CRUD app until you hit a scale where you've got a team of experienced devs, so most people vibing their next 'unicorn app' don't care.
The AI has been trained on what the statistical common practices are. In most cases these are the best practices. What the AI lacks is the ability to spot the cases where the best practices don't work or need tuning. That's where experience comes into play.
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.
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.
When I was a SWE at IBM, Architect was a serious seperate role. There was no scope for me to design the solution - if something didn’t work I could provide feedback to the Architect but only they could change the design. I took a word doc and turned it into code, that’s it.
In 25 years I've only worked 1 place where there were truly architects handing structure down the chain and people were expected to just implement it...and it was a train wreck of an environment.
Every good place I've ever worked, the teams doing the implementation itself discuss it and agree on it in conjunction with some higher lead ensuring that there's no red flags to the implementation. If you're handing things down from on high, you're sending a lot of signals about what you think about the ability of the rest of your team...and none of them are good.
The way I've always seen it in my mind; "hands on just doing coding" work is a Developer, and actually thinking about a problem and requirements etc, and composing a specification => code to solve a problem is Software Engineer.
Tbh I've always hated the developer role, they tend to be ticket bangers who don't give a shit about what they produce; as long as the sprint targets are achieved, (who gives a shit if a tonne of bugs come back in the next sprint(s) eh?).
Depends on the org IMHO; I've always found that Developers appear in large quantities, usually hired from a "low cost economic zone", and are only interested in banging out code to achieve the stated goals in the JIRA tickets.
No independent thinking, no "Actually it would be better if we did X", they simply translate someone else's requirements into code which (allegedly) meets those requirements.
I agree though that the definition is vague, and orgs use the terms interchangeably. If you can't see the difference, then I'm sure that you're an excellent engineer and on the SWE end of the scale :)
My jobs have always been the same, except maybe the first entry-level job I had out of uni. Even then, while I might not have been driving major architectural decisions, there was definitely _always_ the element of requirements gathering, verifying, etc. Never had a job in which someone has said "This is how it is to be done, no questions". There's _always_ questions even with formal requirements.
Agree, regardless of your engineering level, you need to own the security/performance within the scope of your change / ownership. Without that ownership, we're back to the old days where we ship things without caring about how they operate. I don't think that's where agentic coding tools are taking us.
It depends on what “architecting” means. In all companies I worked for, the fundamental architecture rarely moved. I added pieces or swapped pieces out, but we rarely made big, substantial architectural changes.
But if architecting means making decisions for anything, like how to approach any ticket, then yes we very often made decisions.
I had trouble aligning with the second definition and that was probably the reason I bombed a final round previously. The hiring manager asked what is my architecture experience, and I answered that we have principles and staffs so they usually architecture stuffs and we built on top of it. Apparently I should just boast about my 1000 “architecture” experience.
My understanding of architecting is very narrow —- only company level design is architecting to me —- for example designing the whole data platform is architecting to me.
> If that's all your job was, hands-on-keyboard coding with no decision making, yeah you're cooked and need to reskill.
I didn't understand this framing where a person is either a coder OR an architect, but not both, until I ran into a company that operated this way.
All of my jobs expected software developers to make and own their decisions, as well as ship at least some code related to the decisions they made.
The first time I encountered the coder-OR-architect separation was at a company that hired way too many people and held way too many meetings. They separated every responsibility out into different roles and then assigned those to different hires. There were so many roles that they couldn't even correctly identify the right boundaries between, for example, the Product Manager and the Product Designer, or the Project Manager and the Program Manager and the Engineering Manager.
The most surprising thing was how many people at that company liked it that way. The product managers liked writing up PRDs and then making them someone else's problems. The architects would translate those into big documents, then it was someone else's problem. The project managers would do elaborate ceremonies to turn them into tickets which became the coder's problem. The coders took the tickets and wrote enough code to close the ticket, then it became someone else's problem. Eventually the end product became the customer's problem.
I could see how comforting it was. You could settle into a constrained role and, as long you dutifully produced the artifacts of that role, it then left your plate and became someone else's problem. No one person held enough of the responsibility to be accountable for anything, because you could always point up and down the decision pipeline at someone else.
I think these people actually love AI, because it's yet another tool to defer work and responsibility to. They're the people who now point to Claude when something breaks, saying they'll get right on to having Claude fix it. It's one more step in the handoff pipeline and separation of accountability.
At one of my previous gigs the CTO would, in one meeting, bemoan that none of the engineers were willing to make decisions and, in the next meeting, cut your knees out from under you for trying. Even today that same CTO is still in charge and his engineering team is still, for the very same reasons, unable to ship anything.
I'm very grateful that I'm now in a position where not only am I given as much rope as I'm willing to pull, it's expected of me.
Yeah agreed, I have not experienced this as a change in my job expectations, I just have different (better) tools now. It would have been a change if this hit during my first or maybe second job, but not for a very long time now.
counterintuitively, i push back less now that im worried about standing out as "in the way of progress" when management is telling me to push their client manager nephew's vibe code to main
I'm seeing the Architects who only ever handed off a design based off of requirements to the dev and never implemented anything is equally cooked, in a different way.
There's really no sense in handing off the design to a dev to implement, who just copy pastes it into Claude's prompt. The "Architect" now needs to be fully responsible for what goes into production, instead of being able to blame some poor dev who faithfully implemented a flawed architecture design.
AI is flattening architecture and development into a single role.
I always thought of myself as a subcontractor under a GC. It's his job to make overall decisions, build blueprints, shit like that. It was my job to know the vagaries of plumbing well enough to either build what he told me to build or be able to articulate a really good reason why I can't. I might be the plumber one day, the drywall guy the next, the electrician on day 3, etc. Now with the LLM's help I'm the plumber for two hours, the drywall guy 'til lunchtime then I come back and I'm the electrician.
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".
You kinda can, though. What do you think DeadMau5 and other House creators do? They’re musicians for sure, but a lot of their music is 100% in FL or ProTools or Ableton.
DeadMau5 barely even uses his midicontroller as a keyboard to my knowledge, he makes one note at a time I believe.
They’re still musicians and DJs and similar, but they’re one layer removed from pure playing an instrument.
That isn't a great comparison. While composing in a DAW is probably far easier than traditional songwriting, the artist is still the one making decisions about what instrument is playing, what notes it's producing, and when it plays in the track, not to mention deciding how to structure automation clips. In essence what Deadmau5 is doing is functionally similar to programming. LLMs (unfortunately) can also produce these patterns, and at that point there's no human making decisions about the details of the track. Sure you could prompt the machine with exact specifications of the song you'd like to hear, but ultimately the "decisions" are made by the model.
How is this comparable in any way? A better analogy would be a musician that now has software that generates short sequences of the song and they choose whichever fits.
That's exactly what musicians who purely use software do already. No one hears a song in their head and programs it note for note. They constantly add small elements, tweak them, and then listen to what was added or changed, over and over. They are hearing short sequences of the song and choosing what fits, according to their taste.
I know this is a joke, but anyone who can actually play theremin is probably in the 99th percentile of musicians in terms of practice hours and raw skill.
It's weird seeing software devs, a highly educated workforce, get labor relations and labor history so wrong. The idea that our industry will keep paying high six-figure salaries will quickly come to an end unless we collectively act together.
The idea that rationalizing a job more (relying on metrics, measurements, statistics, predictions) will lead to better labor outcomes is foolish. We are only paid well as devs because we have comprehensible jobs (ones that require specialized knowledge and understanding).
We have over 200 years of history regarding what happens to labor when their industry becomes more rationalized and it has never ever benefitted labor once in the history of capitalism.
Yeah, it's incredibly bizarre that people are like "no we will get more valuable, see how much more we can do, we're more productive than ever!!!" when what's actually happening is the thing that you previously had a monopoly on (skilled software engineering) is vaporizing in front of you and the people writing paychecks haven't quite figured out how to value your role. It will leave a very large number of people behind entirely.
Imagine, as the tractor was arriving on the scene, a farmhand saying "we will get more valuable, see how much more we can do, we're more productive than ever!!!". You seem to be saying the tractor will make their farm labor less valuable. Which is true. But they're saying that the tractor freeing them from the field allows them to move on to more valuable activities, like software development. It is undeniable that software developers have been far more economically valuable than they would have been as farm laborers if the tractor was never invented.
Of course that is conditional on "software devs, a highly educated workforce" being true. If it is true then "we" are well poised to leave software behind to jump on the next big opportunity, but I suspect it isn't actually true.
> You seem to be saying the tractor will make their farm labor less valuable
It did, it lowered the price of the end product, so the scale needed to increase to make the same amount of revenue with the ultimate consequence of there being less farmers necessary to sustain the demand for their crops.
> they're saying that the tractor freeing them from the field allows them to move on to more valuable activities, like software development
Surely you see the issue with this reasoning. In aggregate it allows society to 'rebalance' where labor is deployed over generations of time, but at the individual level it just leaves people jobless and eventually poor.
> Of course that is conditional on "software devs, a highly educated workforce" being true. If it is true then "we" are well poised to leave software behind to jump on the next big opportunity, but I suspect it isn't actually true.
Or it results in a further shrinking of the middle class and dramatic increases in inequality.
The real question is at what point does software saturate the demand. I personally thought that the market was already heavily saturated before AI, which does not bode well for career software engineers.
Also, if AI can write software, create art, run a business and detect cancer in scans, better than any human what exactly is left for humans to move "up" to? The transition from farm labour to software was just blue collar to white collar, physical to intellectual. But if machines have taken the physical work and AI has taken the intellectual work, what exactly is left for us to pivot towards?
Taste was the answer that we agreed on a few years ago. Being able to choose the best output or know when things are off. Having design sense and the tenacity to dogfood the output in order to fix the things AI can't see. It's like a combination of a design lead role with a QA role, you have to know every feature from the perspective of a user, sense where there is friction and confusion and know how to do it better. Maybe calling it a "director" role would be more apt since that combines creative vision with hands on, detail oriented work and directing the work of others to redo the product until it is right.
In that analogy, current developers are more like the horses that pulled plows than the farmhands. Anyone noticed any horses on the gigantic industrial farms doing "more valuable activities" lately because the tractor freed them from plowing?
The farmhands are closer to product managers and architects but none of them are former horses.
Do you consider horses (any horse) to be highly educated? The earlier comment already recognized that the lowly educated are unlikely to find their way.
If it is true then "we" are well poised to leave software behind to jump on the next big opportunity, but I suspect it isn't actually true.
Much like discretion is the better part of valor, if your plan in 1916 is doing a gallant feathered cap cavalry charge at the machine gun nests, don't worry too much about whether high command will promote you up the ranks later.
Luckily that’s applicable generally to most desk jobs with AI replacements, as long as you accept the shit ass quality that clankers produce when unsupervised.
Either the AI bubble will pop because unsupervised clanker quality never reaches supervised levels or we’ll ALL be out of a job and then it’s the everyone’s problem when society crumbles.
The only way to keep programming a high-earning professional is to make it a licensed job. Like doctors. You'll have to have a formal degree and get a license to push any code to production, or you go to jail. That's the only possible future where programmers still earn significant more than most desk jobs.
That'll force most of us to leave the industry, of course.
So I couldn't just casually make an app? That's always been the problem with licensing. Some company has a bunch of licensed engineers buildings some software app, and then a bunch of kids comes along and makes something similar and it's better so people give the kids their money instead of the licensed engineers.
You can, but you can't sell it on major platforms. Just like you can build your own house on your own land without a contractor license, but if you sell this service to someone else a license is needed.
why do you think helpdesk or call center employees were not able to unionize and protect their jobs?
in the age of AI, the helpdesk/call center is really not different from that of a software engineer. The only diff is Helpdesk operator talks to a human. SWE are now just talking to LLM.
the job is perfectly mobile, can be offshored, outsourced, replaced, and million other ways to destroy any attempt to unionize.
unless, the society-wide labor unites as a single voting block for more redistribution from capital towards labor and universal federal ad-valorem wealth tax, instead of income tax
yes, its gotta be either total socialist/peasant revolution against the Big International Capital or nothing.
International Capital has advantages: it has power, it is fluid and mobile, can work across geographies, tax codes, it has natural cooperation incentives against the labor
Detroit and many other factory and heavy industry jobs collectively acted through the 20th century, which raised costs, slowed production, and simply accelerated their downfall. Introductions of any significant trade protectionist follow-ups ended up being scorned by the public (see the popular reaction to Trump 1, Biden, and Trump 2 tariffs regardless of efficacy).
The medical industry achieved some protection through regulatory capture, licensure, and throttling education. Doctors have very high salaries now but there's a shortage and they're overworked. Innovation is also throttled in that space as a result. Socialized systems aren't faring any better, the doctors I know in Canada and Japan are just as overworked, have to rush cancer patients through 5 minute appointments, and are paid far less.
There is no magic bullet for making a large profession sufficiently protected by mystification (anti-rationalization?).
I reject the notion that only the elites know how to run these society impacting technology companies. These people are anti-human and should be imprisoned. Workers of these companies should be able to elect their own leaders, their voices are worth more than the investors or shareholders.
The economy is the only place in our society that we allow tyrants to openly reign freely. We only have our entire existence as a species to know that monarchies, oligarchies, and authoritarians have hindered our capabilities to thrive as a species. There's no reason why these companies shouldn't be subjected to democratic norms too, they couldn't exist without our democratic societies in the first place; the expectation that only a select few elites should dictate the direction of technology in the US is deeply concerning and should be rejected with something better.
Workplace democracy is better.
---
Fun fact, Congress can impose that corporations become workplace democracies and it's totally legal. Whoa!
Don't let the anti-humans tell us how to run society. Society can be so much better if we rid these anti-humans from our ranks.
> The idea that rationalizing a job more (relying on metrics, measurements, statistics, predictions) will lead to better labor outcomes is foolish.
The interesting thing is that this exact thing happened before in the software industry. It's what killed the "old" software giants of the 90s. Only really microsoft was able to pivot and recover.
"Big Tech" became big tech by bucking that trend and being much more empowering to "low level" employees. Allowing talented people to build good things. They ditched the measuring productivity with "lines of code" and tickets closed and all that nonsense that was common place before that.
The current batch of tech CEO are going down the same path of morons like Jack Welch and we're all going to pay the price for it. I guess, if I were them, it's a reasonable choice. Despite leaving a wake of carnage and turning great companies into shells of themselves, they'll be billionaires before anyone figures out how utterly fucking stupid they are.
It's just very odd how, as an industry, we learn nothing from the past. Not at the executive level and not at the worker level. It reeks of arrogance at all levels.
You'll notice the parent didn't saying anything about unions. Unions cannot help here, but collectively working to establish a legal professional designation (think doctors, lawyers, etc.) can.
Those professional designations maintain value because they have a very, _very_ high bar for getting and keeping a license and also are burdened with liability for malpractice. Most current developers would be filtered out.
frontier labs are the ones who are working collectively to kneecap competition (open weight models), and ensure regulatory capture towards themselves (employees of the frontier labs)
you are barking up the wrong tree with that unionization horse apples. Unions plus technology do not go together. i’d rather take my chances on my own than deal with all that nonsense. What’s up with the the streak of communism in the comments lately?
When you look at everything and only see communism, you just don’t actually have a cogent definition of communism. It’s a common problem in American political discourse. Anyone left of Clinton is called a communist in American politics.
Well no, ai music has promoted musicians to publishers, designers to art directors and developers to software engineering managers.
It’s just creating your own team of little robots working for your own personal “department”.
Though what I am seeing is that increasingly I am “setting up teams of agents” which each have their own “lead” and I just talk to these “leads” not individual agent “developers” . Effectively becoming a “VP” of engineering of my own private little “consultancy” … maybe next year (or month?) I will manage a bunch of “vps” as the “ceo” of said mini organisation … a product engineer indeed.
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.
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.
I would be cautious deferring to LLMs' judgment in long-horizon architecture or the more procedural, threat-modelly/incentives side of security, or any other large scale judgment calls, because they simply have no experience with them.
RLVR in these domains (which I think is mostly synthetic end to end, including grading) is turning them into Idiot Savants so jagged in understanding and performance that they defy human expectations for what kind of knowledge and behavior correlate (causally). A human engineer superhuman at hill-climbing low level performance would be at least 95%ile at at general architecture, since they're the same problem just at larger and slower scale.
There's no hyperbaric benchmaxxing chamber devised for tasks of this scope or ambiguity yet. They fall back to platitudes and best practices (the "Reddit"/HN part of the weights). In my opinion, they are just kinda "ok" at architecture. When you're in the pocket of what they've spent more time learning in parallel than any (or all) humans could, they just let their freak flag fly, and you know it when you see it.
Here is Claude from this morning writing and pruning a pure x86 ASM implementation of symmetric DTLS/symmetric UDP, down to a 3.8KB binary, completely from scratch, in 3hrs of nonstop work: [0]
No human has or will ever be able to do this. But any who could even appreciate the difficulty of it would think "why TF did you do all that work before implementing certificates!" But Claude has literally never been trained on >1M tokens of consequences so
Who do you think a business leader will listen to, someone disagreeing with them or an omnipotent super intelligence that validates every idea of theirs?
That sounds like a false dichotomy with a bit of emotion behind it, and I'm not really sure what it has to do with long-horizon jaggedness.
I do think that once long horizon software architecture can be brought in-distribution with larger memory pools and better architectures for long context, RL will be just as effective at teaching them to be superhumanly better at it, or to at least have vastly more breadth of knowledge to draw from, as long as the cost of bad decisions can be used to provide feedback to the model in a tight enough loop.
Investing and business decisions have just as verifiable and large scope + a tighter verification signal (profit), so it seems arguably equivalent in scope and difficulty as general economic decision making.
At that point you might as well ask why boards even have CEOs or why shareholders would rather have humans interfering with their assets rather than just asking something super-intelligent.
I could be misreading your comment, but I think if you want to be who a businessperson turns to when they need help with something important, you should at least be able to articulate and show where and why you can provide better guidance than SOTA AI.
If someone snarkily dragged their feet on AI as a source of knowledge at all, even as it becomes obviously more skilled in at least very-adjacent areas of work, without justifying why, I think that would be discrediting. If someone felt like you were on their team, and generally perceiving the same reality as them, but perhaps having useful insights that AI (and everybody else with access to it) doesn't also have, I don't see why they wouldn't listen to you. Basically, you should give people a reason to want your expert opinion if you want your job to be providing expert opinions
> and I found in review that Claude would leave the debugging tooling around unflagged
Why is Claude to blame for that particular decision, if you created it? That's what this is about - you need to constrain the design space to take responsibility. In this case, understand the debug tooling and what it should be doing. Negative prompting is rarely a good solution.
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?
Agreed, and another point that I haven't seen in the article : 'architect' as a separate software engineering role was a bit of a bad word, even if everybody agreed that architecture was important.
It was mostly because in some companies there was a cast of 'architect' who were seen as above coding, and who mostly delivered out of touch UML diagrams, or ill-fitting data-structure. The core of the issue was that even good programmers would rust and get incapable of understanding the ground truth if the organization discourage them to also be in the implementation side.
Here it's not exactly the same thing with AI, since the loop is dramatically shorter, but the (lack of) feedback issue remains.
I really believe that my added value as a programmer was fundamentaly to evaluate technical tradeoff of the different options to solve a business issues, and them to implement them. Now with Claude code I'm infinitely faster at the implementation part, but I'm also eroding my capacity to evaluate those tradeoff.
Programming is a medium, and you also need to work with it from time to time in order to keep some level of competency. And yet in many companies we are basically forbidden to do that.
I feel that we have been given cars, but have also been forbidden to ever walk again; Sure the car is more efficient most of the time, but there's a an almost-vital reason why we have to do jogging to compensate.
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.
I'm also still seeing really poor performance with architecture, with Opus 4.5. I feel architecture is the only remaining use for me, besides the project management aspect of it all.
I give that a bit over a year, then me typing, or even reading, the code will just slow things down.
I see this sentiment a lot. "AI will replace us but only if used correctly". The "only if used correctly" is the SWE+Architect part that people miss. So effectively, you may be contradicting yourself in this single comment.
we went from "humans transform vague requirements into semi-technical requirements into code" to "humans translate vague requirements into semi-technical requirements that AI turns into code", the next step seems hardly different to me
Heh, at every company I've ever been at, an Architecture role is about the same as a non-banking VP, definitely not a demotion. It's often substantially more pay with substantially less work.
Architect very often was a coveted sinecure for failed programmers. It didn't necessarily pay better than a senior IC and they normally had no reports.
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.
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.
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 ?
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.
I've spent 4 years in a team of idiots who earned twice my salary because they were hired when company was desperate, while I have lower position and salary because I was late to the party. We spent countless hours doing stupid shit that was never meant to work and nobody wanted, and we shot down projects that later upper management deemed priority. I am tired of fighting people who never fucking listen and aren't capable of long-term thinking. Oh wait, they are. Because most management roles are a game of hot potato where the goal isn't to defuse the bomb, it's to make sure the shit doesn't blow right into your face. A random guy making the right calls is a danger to a team of useless fucks. They understand that very well. Another colleague who is highly skilled was literally told "go find another job if you want to make a career".
I am out of fucks to give. My goal is to minimize the amount of energy I put into work. I don't push back, I do what I am told to do, and I take my sweet time to do it. Of course I cannot jump ship because job market is not what it used to be. Hashtag fuck work.
Has this really been your experience, in practice? With prompts this vague, I often see massively complicated preemptive optimisations.
If you feed in the right info on what sort of performance optimisations make sense given the context of the system, and provide the mechanisms to measure them, then yea.
'make sense given the context of the system' doesn't feel solved to me.
With Opus 5.5, it really has. I’m pretty sure if you fed the code the article was written about to it and gave it that exact prompt, it would flag the extra API calls. More context is better of course, but I’m regularly amazed how little context you need these days.
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
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.
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.
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.
The people who "talk and send emails for a living" are the ones actually driving value in the company and always have been. And they've been trying to automate your job away for decades.
>"The people who "talk and send emails for a living" are the ones actually driving value in the company and always have been. And they've been trying to automate your job away for decades"
Trust me, I know. But for a long time they needed us to do this thing we really enjoy doing, and paid us well for it. I don't care about driving value for the company. I don't want to be one of them. I want to do something I enjoy and get paid for it, not pretend to care about something I don't. So now I have no idea what to do.
Their jobs aren't far behind. At this point, I'm all for AI accelerationism. Let it all burn down. Nobody cares until it's their life on the line anyway.
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.
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
may i ask what benefit you envision from your suggestion? im not seeing the negative aspects of using a masculine pronoun in referring to a male humanoid.
> 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.
It's a pretty normal failure mode in teams. The abstraction breaks because the developer doesn't know the things that drive their latency.
Is it database requests? RPCs? Is there a function call which is computationally expensive?
Teams then respond by making rules to help make slow things stand out "no RPCs in functions, no synchronous RPCs, only 1 database read per request, don't call this code in a loop", etc.
Caught before merge? Only if you have someone really familiar with all the abstractions _and_ the team's previous failures reviewing it. Otherwise, developers are always finding new ways to write slow code. :)
But, that's why we have feature flags and incremental launches.
That’s not just a continuum but also a timeline. Junior devs need to be encouraged to start thinking about why as much as what, and what more than how.
But they don’t teach you that in school. You get how and a bit of what. Maybe a little why in a sales pitch or an aside from a professor who hasn’t worked in industry except in research which is prototyping and we all know how people who only do prototypes are about rigor.
"AI, create or improve software to make money for the company. I repeat, the ultimate goal is to make money. I don't care about any details, like architecture. Now start!"
Depends what "it" is, but for a lot of web SaaS companies, probably quite far. Think about thinks like Trello, Workday, Greenhouse, Zendesk, Jira etc. Definitely doesn't take much technical expertise to vibe code replacements for those.
The thing is that most of us don’t have the patience to wait for the toddlers in ties to fuck around and find out. We have tuitions to pay and retirement funds to fill and we don’t want to be subpoenaed.
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!
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.
This isn't even backlog grooming. It's up to me to create the backlog and all the analysis that goes with it, plus the stakeholder management that PM are typically supposed to do.
I think I’ve attended a lot more dysfunctional grooming sessions than you have. Magic thinking is very common and you have to send a lot of feature requests back to specification until they get the message and stop coming to you with hot garbage.
I've had good PMs that have managed this. On one team it was so bad the PM told the business they had to do an ROI study for any suggested change. What a glorious time as a dev.
> We're gonna get promoted so much, you may even get tired of being promoted. And you'll say, 'Please, please. It's too much promotion. We can't take it anymore...'
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.
Yep, I regularly get into conversations online where people are claiming that AI can't do their work, and theirs is a complex and important problem in the real world.
Chances are, if you can't get AI to do it, it's because it's a problem with internal contradictions that can't be resolved in any logical way. For anything else, there's AI.
Architecture is not hill climbing. Confusing the two is why software becomes slow and bloated - you believe low hanging fruit can fix all problems. They all end in local minima that I suppose is fine if nobody knows any better but users aren’t stupid. They can see that a similar app works 3x faster.
Exactly. Architecture is about tradeoffs. If you dont compromise on one of properties in CAP theorem for your database, then AI will reinvent Google spanner and expect you to have Google scale data center to run it.
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.
reply