We promoted developers into architects without informing them
manidoraisamy.comLol, sounds like something only a junior developer or intern would say.
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.
I give that a bit over a year, then me typing, or even reading, the code will just slow things down.
It's incredible!
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.
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.
That's where we disagree
Love that attitude!
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.
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.
And yes walking is refreshing and should not be taken away.
People who did not have the opportunity to grow and learn how to think about problems are in a bad spot right now.
They aren't the ones holding the vision how the blueprint is going to materialise.
The cogs in the machine, thankfully for c-suits, now they can be replaced by real cogs in the agentic software factory.
[and your director now is convinced all his stupid ideas are both brilliant and very safe]
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.
Try that with photography, painting, or music: "AI music has promoted musicians to architects".
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.
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
"The emancipation of labour is neither a local nor a national, but a social problem, embracing all countries in which modern society exists."
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
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.
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.
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.
Few creative insights come from management.
Same place the economy has already been going for a while: Looking the other way.
In other words, those with resources get to buy the ability to do things that are unacceptable or illegal for everyone else. The job is to accept it.
The farmhands are closer to product managers and architects but none of them are former horses.
It is true that the poorly educated don't understand how to build meaningful relationships. They are destined to become the modern horse. But the highly educated aren't sought after for their brains. They are sought after because they're fun to be around and can share compelling conversation over a beer at the bar. There may be an AGI future where it too can build relationships, but AI is not that.
I would also ask, even for those who can adapt, what exactly comes next? It's not remotely clear where and what could absorb the legions of "tech people". It's kind of like the people that jerk off self driving trucks, when you realize how many people are employed as truckdrivers (hint: in many states it's the most common profession) and ask "where the fuck is this horde of people supposed to go?"
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.
That is hilarious seeing how unions literally became a thing as a result of the industrial revolution.
Unless you're arguing that the industrial revolution had nothing to do with technology?
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.
I don't think that's going to work. There's no barrier to entry for vibe coding. Your union would have to include everyone in the world.
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?).
https://en.wikipedia.org/wiki/Workplace_democracy
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.
consultants, laywers, bankers, accountants, auditors, some other high flying professions organize in a Partnership format.
its functionally no different than being a cofounder of a startup
That'll force most of us to leave the industry, of course.
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.
"you can't sell phones without X% domestic software", "you can't share security vulnerabilities overseas", "part of X compliance policy is domestic sign-off", etc
is this a good idea? Different answer than if it'll work. But a market like the US has limited window of time where it's a sufficiently major economy that putting tariffs and policy up to protect an industry may pay off. The US has by far the biggest software industry, so protect it (the labor force) while you can.
Sounds crazy to anyone who grew up in the post-1990 economic system but that is how it worked for the UK and other countries under Bretton Woods
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.
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.
You're still in the driver's seat, sure; but I think for many uses of AI for coding, you're also still in the driver's seat
I only meant this part:
> Try that with photography, painting, or music: "AI music has promoted musicians to architects".
And nothing else. I am absolutely not intending to insult deadmau5 or anyone in the music industry. I was trying to make a point that they operate “one layer above” and it’s fine
That is where you're wrong, kiddo
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.
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.
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.
AI is great when you know what is needed. But even if squeezing some more juice doesn’t happen, even if capabilities improve, and somehow the economy doesn’t collapse, the utopian world will be far more idiocracy than Star Trek. AI may run the world in a fairly benevolent way but the population won’t have a clue what to ask for, or be able to anticipate the problems their requests make.
Or perhaps enshittifation destroys the AI world and everyone moves on.
We develop an internally-used information system (think of like a CMDB, some automation around it, plus some other parts that aren't typically part of a CMDB, like employee timesheet). There are semiregular requests for automations at the edge, for example a non-technical user might need to create several hundred objects, and there's no existing tool for it, but there is an API. We could task the junior developer with writing a tool that does an excel import and creates the objects through the API. Stuff like that.
They can then decide if they just write the tool, or also talk to the stakeholder and get some feedback and/or suggest different file formats that work better for this application, and so on. Plus they develop experience with our API. They also get feedback through code review.
When that works well, we try to bring them closer to the core business logic. There they have less autonomy at the start, but it increases when they show good judgement.
This might not work for everybody, and we certainly wouldn't have enough work to employ three juniors with such tasks. But in our niche, it's successful.
It’s a better way to get a bus number of three for the mission critical parts of the code and let the rest go higher, and reduces bottlenecks in the backlog. It was in part a reaction to how poorly I saw Gantt charts behave in practice. I felt it was better to remove the obligation to use them rather than to keep tolerating the farce.
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.
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..."
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.
Now with AI coding, it pisses me off even more.
Because if someone requires instruction on the level of "modify function x_y_z() in python_file.py...", then it's highly likely they won't be able to fix the failing tests without making things worse, nor would they able to address to other teams' concerns.
In the less extreme cases, people might be able to do follow-up work, but since they do not understand the reasons for the design, they won't be able to do it properly. Eventually system will become so wrong, it will fail, and you will again have to spend lots of time studying how it evolved and writing those super-detailed tickets.
Still, is it worth delegating the tasks? Before the AI, the answer was yes. Sure, you might be losing time by delegating simple tasks, but the other person is getting more experienced, and there is a chance they might become a proper software engineer. With AI however I seem to see some people just stop learning new stuff, being a human AI wrapper, which is very troubling.
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.
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.
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.
...which makes them very replaceable by a coding agent.
Your example is great, but if you also ask an engineer when can that be done, they need to already work out the approach, analyse any gotchas, maybe even build a PoC — easily taking 50+% of the effort to give you a response.
This is more of a comment on the industry as a whole, but your approach is the sweet spot IMHO: do something that fits in two weeks.
This encourages people to figure out small incremental steps that leave less important stuff for the end — as they probably won't get done — but not everybody is fine with this open-ended approach. Because taking ownership also means assuming accountability.
If someone never shows that initiative though, I’ve never known a manager to push them more than once or twice. Eventually everyone in a team finds a rhythm that produces some amount of forward momentum and that status quo stays until someone decides to shake things up again. The shake up might not even be big but it also doesn’t have to be world changing.
I’ve had to recognize this in myself over the years. If I want to have more responsibility in most western organizations, I need only reach out and take it. Everyone has exactly as much work as they want (which for some people might not be very much at all!) and once that clicked for me, I stopped letting the acts of others at work control how I feel about my own performance or output.
To tie it back in, I personally see those small steps of tasks as the ladder towards responsibility. But if someone has never climbed a ladder before, it’s important to remember that climbing is exposing them to a new level of risk that everyone will respond differently to. Some people like taking risks! And they are often rewarded for it, but I can also respect someone who responds to that risk differently.
These aren't software engineers, they are just people that know a programming language syntax.
These are the people getting hired over me?
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.
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.
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.
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.
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.
may not be related to the way it was developed and more about the perspective of the person looking at the code
The main area where I spend influence on really shape the outcome is on process and team culture, not any specific technical decision.
The goal is to steer the high level design of the system over years. You could do it by dropping docs on people with little interaction (arch by decree), or you could steer the teams and people. Help them get to the right answer “on their own”.
They also say stuff like "Dont't even joke about using PG. We've just sunken $xM into Oracle licenses and HW and it would make us (me) look bad."
Unfortunately, that seems to be the general direction product people took... Glad I'm out
In a Service-Oriented-Architecture it is important that the service boundaries are controlled by someone without a feudal stake in the implementations. But probably the only architects who could come into a new org and do that would be ones who grew up in the same domain in a different org.
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.
A big reason is that they're always trying to hire the cheapest possible developers, with corresponding skill levels, so a big part of the architect's task becomes to try to impose some sanity on the collection of issues that result.
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...)
> 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
preach brotha!Most of the time I see these roles not operating well, the same way any role can suffer incompetent middling behaviour. There's plenty of terrible SWE as well.
As a lead developer I'd take a good product manager, scrum master and architect in a heart beat. A bad one, never.
Large scale software development is just a nested series of architectural choices from top to bottom.
That some organizations choose to give some software developers the job title of architect is not a ‘bad meme’, it’s a reaction to the realization that there’s a lot of architectural decisions being made and it might be nice if all the people making them had sufficient information to make them right.
Good ‘architects’ focus on making sure developers who are making all those architectural decisions have the right context to make them.
Bad ‘architects’ try to make - or preempt, or second guess - all those decisions that have to be made. That doesn’t scale and doesn’t work.
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?).
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 :)
Sidenote: note that in some countries someone with a degree in Computer Science cannot legally call themselves an _Engineer_, even though they have roughly the same knowledge and abilities as someone who got a Computer Engineering degree.
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.
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.
So whenever i hear that coders are out of job because of AI, I always wonder where were those “coders”. Never met one
Rigid roles are a reflection of a human desire to put people in tidy boxes, that doesn't mean those boxes map to reality in a useful way.
It's a sharp contrast, and a weird contrast, and in the latter case, you're constantly challenged, constantly finding yourself outside your comfort zone, learning your limitations, what you like, what you dislike. I'm really really glad I didn't end up landing at a large company like I used to work (Symantec). Some people like that structure. I can't stand it.
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.
Eg. some of that flows into Python proper (see eg lazy imports), but with the amount of Python code, I believe LLMs will continue offering suboptimal, non-engineering Python for the foreseeable future, and prompting them to do otherwise is an uphill battle.
I believe similar holds for JavaScript — incidentally two of the most popular languages in the world.
I did not like that very much, and did not stay too long.
I recall sitting in an all-hands once where the engineers were bleeding out their eyes about the abomination that was the new start screen, while the head PM just kept repeating, "This is the right decision. WE HAVE THE DATA."
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.
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.
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.
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.
In the real world you have mechanical, civil, electrical, and structural engineers who need collaborative and clear points of interface and agreement. That and coordination of individual deliveries and customer need mapping, are what Architects do.
The title is misused in many software contexts, but the fundamental job is real, and necessary, and profitable.
To be fair, I've also seen some pretty bad decisions by original architects/developers, although it's easy for me to criticize in hindsight.
No, but AI and overzealous juniors made this way harder to argue about overengineering, technical debt and bad/hard to handle architecture. Plus our team manager/PO changed a year ago for one who really like 1 on 1 calls, so that you learn about the new hire is working on during the daily. The stuff you argued during your own 1 on 1 call was a bad design.
As best I could tell in that org the tickets were highly detailed and rigid - data model, API calls (both interfaces and expected external calls) with technical product manager and tech lead basically creating these. The rest of the team then seemed to just be plumbing/following the script. I only got a brief glimpse so it's possible that I got the wrong impression, but it felt jarring.
Agree that anyone working in this way should be looking to make a change, as it's really not a leap for those tickets to be implemented autonomously now.
Needless to say we completely ignored him and just spoke to the product manager and created our own tickets.
I've literally worked in feature film production, spacecraft, and now optics and medical device industries. My education was in straight computer science - but my opinion is that it behooves you to basically be learning from other people all the time and bringing your ideas to the table, and you're paid to help the company succeed at a high level. I always called myself a software engineer because that's what I felt most formally confident at, but honestly I don't think my day-to-day matches what other people mean by it.
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.
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
[0] https://claude.ai/share/90de9350-81f9-46ea-a628-be625e8b9a7a
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.
You'll get review comments, alerts, static analysis reports, secbug tickets, etc coming out your ears with even a modest amount of modern tooling.
If you weren't doing it, you were doing it wrong.
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.
Architecture is a responsibility shared between your project leadership, whether you call them leads or principals.
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!
functionally similar
I’d say very few developers are really good architects because they rarely had the opportunity to grow and trial.
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 don’t hate the PM role but some stakeholders are so…ah don’t want HR to find me here, right?
The more I play this game the more I want to squeeze into lower level programming careers where stakeholders are more technical.
Jesus, this is gonna end up being middle managers all the way down. Get a grip!
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.
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.
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.
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.
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.
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...
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)
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.
Well, if this is what people were doing, I'm not surprised they think that "software development is solved" or whatever the current line is.
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 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.
I might be native but I believe things will improve/stabilize and we won't have the apocalyptic disaster often described. Hang in there and some new possibility will show up eventually.
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.
I cope by hacking on educational kernels. I still use AI but only for discussion or I couldn’t figure out something after exhausting every other venue after say a few hours (if it’s a tool issue) or a few days (if it’s a programming issue).
Just spent a few hours trying to figure out why the Makefile doesn’t work. I’m much happier now. I don’t need to talk to a stakeholder to fucking understand the business logic of a 37 lines of CASE WHEN THEN ELSE END. I just need to understand the kernel and tread lightly. I scratch my hair way more often for the kernel but I feel young.
I used to get my dopamine rush from coding. But coding today isn't what it used to be - even before AI. It has become more of a jigsaw of many systems where you're mostly plumbing pieces together. Way back, we wrote entire systems from scratch building on top of very little. Today hardly anyone does it. Now AI gives me the power again to translate big visions in my head into working systems. I don't have to write all the code myself. But without AI I might not be able to do the things I can do today.
Now I'm in an AI first job, but before that I was still doing ones where coding was pretty good - building interesting complex things and always finding new things to learn.
I'm really not sure what I think about promoting all day.
I need to work out how to optimise the work to be fun somehow, I don't know if it's even possible.
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.
> "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...
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 ?
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
Programming is a lot more than knowing syntax and APIs.
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?
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.
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.
This app has millions of users…
Solved.
The market for dedicated architects has always been vanishingly small.
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.
It does seem to me that had I been vibe-coding this whole time, it is unlikely I would have improved as an architect.
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!