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

There are no comments on this comment yet.