<- Back
Comments (128)
- whycombinetorAm 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.
- uptrailsNo 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".
- nixpulvisI 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.
- bikeshavingI’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.
- pjmlpThe problem is that usually each team only needs a single architect.What is happening is no different when developers got promoted into team lead of the offshoring team.Which also didn't require that many team leads onsite, and off they were, everyone else that wasn't leading any offshoring team.
- mellosoulsA dev moving down to architecture is not a "promotion".Architecture is no more immune to AI than software engineering.OP is describing somebody using AI poorly, and seems not to have a great handle on the way all jobs are impacted and boundaries being wiped away.
- dhpeIt 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.
- kaffekakaI'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.
- bengold14Couldn't agree more except that these are architects that are actually implementing and need to deal with the pesky details of building. Engineer-Architects.The problem is the abstraction we still expect them to use is code. In most companies architects didn't use code at all. We need a new abstraction that focuses on architecture.(full disclosure I work in this space https://www.archme.io)
- lordnachoIf 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.
- spacebearA basic prompt like “is this code performant?” would probably catch this problem with current models.
- hopppYes. I have been an architect all along, but I needed to write the code. Now that coding is solved I can fully devote my attention to architecture.
- ramesh31I'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.
- smrtinsertWe were always architects. They just dont want to pay us for it.
- 6thbitSorry but Nah. Architecture has always been a part of the job.If you weren't doing it, you were doing it wrong.
- bluefirebrandI don't view becoming an architect as a promotion :/
- LeafItAlone> Since logging was the first line to execute after installation, the welcome screen took 15 seconds to loadIf 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.
- zug_zugExactly. You are now PM, Architect, and QA but get paid the same salary[and your director now is convinced all his stupid ideas are both brilliant and very safe]
- jimnotgym"Monitoring new customers is the most important part of running a business"I'm afraid I can't let that one slide. Where do we start with this.Is it more important than having a good product to sell, for instance?Is it more important than maintaining your existing customers?Is sounds so creepy to me, monitoring customers...
- giantg2It 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.
- throe839384949I think we should not promote existing developers!If AI is even remotely capable, we should fire all staff, and hire the same number of people in Nigeria! Diverse workforce is by far the most important goal! And it reduces CO2 emissions from commuting! And we save money!
- Animats> Monitoring new customers is the most important part of running a business...Priorities.Useful question for "analytics" people. If you only collected data for every thousandth customer, would you have less useful insights?
- themgtYesterday, 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.
- j45The role of developer is evolving, and it doesn't means developers scale into architects automatically. They get to learn, which is great.
- gspr"Promoted". Some people wanna do.Jesus, this is gonna end up being middle managers all the way down. Get a grip!
- 0c3ca83Architect was long considered a bullshit job for the out of touch.
- viklove> If you are a senior developer or architect who understands the number of API calls behind each method, you would have:Lol, sounds like something only a junior developer or intern would say.
- heybax[flagged]
- atombytede[dead]
- chmorgan_[dead]
- sick_of_slop[dead]
- tschellenbachActually, you should always hill climb security and performance. AI can optimize these things if you ask it to.
- solyin> You got promoted. Nobody told you, so I am telling you.Love that attitude!