News for hackers. Stuff that matters.
Re:We promoted developers into architects without informing ... by sdevonoes on Friday November 20, 2026 @04:28PM (#50582428)
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

Re:We promoted developers into architects without informing ... by switchbak on Friday November 20, 2026 @04:52PM (#50582783)
I've worked with folks who seem to identify as that being their job - but I don't think anyone ever wanted them to work that way.

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.

Re:We promoted developers into architects without informing ... by Pokepokalypse on Saturday November 21, 2026 @12:11AM (#50586149)
After you've worked at large companies (who tend towards defined roles: tidy boxes), and small start ups where - you do what needs being done; sometimes that even means a coder is doing demos to potential customers, or even investors.

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.

Re:We promoted developers into architects without informing ... by onion2k on Friday November 20, 2026 @05:09PM (#50583010)
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 closer 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.

Re:We promoted developers into architects without informing ... by spiralpolitik on Friday November 20, 2026 @06:29PM (#50583853)
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.
Re:We promoted developers into architects without informing ... by marssaxman on Friday November 20, 2026 @05:52PM (#50583496)
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.

Re:We promoted developers into architects without informing ... by steelframe on Friday November 20, 2026 @11:04PM (#50585822)
I was there during that same period of time. What you experienced was largely due to the PMs wresting control of the company from the engineers under the direction of Ballmer. The result of that was Windows 8.

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

Re:We promoted developers into architects without informing ... by antonvs on Friday November 20, 2026 @11:18PM (#50585901)
My headcanon is that the reactions to Ballmer's monkey dance and "Developers, developers, developers!" pissed him off, so he started to look for ways to make them less important.
Re:We promoted developers into architects without informing ... by 43920 on Friday November 20, 2026 @08:52PM (#50585040)
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.

Re:We promoted developers into architects without informing ... by hibikir on Friday November 20, 2026 @09:57PM (#50585467)
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.