Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.

 help



Truly horrible architects tour conferences, make their orgs purchase unnecessary proprietary tech stacks sold at those conferences and then force new projects to utilize them, adding busywork both while adding support and then ripping it out once it is clear that 90% of the stack won't even support that cringe proprietary tech that's out of fashion the next year.

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


This is a totally different type of architect, the "enterprise architect".

Same with AWS architects. "We're pretty much stuck given our savings plan for Aurora - don't even mention PG."

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.


Thats a technical lead,no?

Yep. Most people had job titles that didn't fit their roles, and then assume that is what those positions meant. I've had people tell me they're architects and they were middling devs at best, but everyone is limited by their own ceiling

There is a lot of overlap, at least there should be.

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


I really hope AI eliminates enterprise architect roles. It is uninspiring to get direction from people who don’t do anything or build anything.

AI will allow them to implement their vision without pushback and complaints.

Absolutely. I've seen Claude polish turds really really shiny.

I've also had coworkers produce garbage and then be totally proud of it.

may not be related to the way it was developed and more about the perspective of the person looking at the code


Nobody cares about the code, they care about the outcome.

Maybe the outcomes will be worse, but that will be on the person driving it.


I'm sure they will blame all the inevitable issues on the AI.

I think it won't. At least I don't see how.

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.


The agent won't complain about being uninspired, so I guess it is your role that is going to be cut while he just gives the direction.

Bad architects insist you add things like websockets because they already put it in the Powerpoint.

And the bad architect also insists on finding a use case for a technology that either they developed when they were an engineer, or technology that was current at the time. Usually the architect has little knowledge of current best practices in industry.

Bingo. Same thing with product managers. My worst experiences as a PM were when my boss insisted I had to call the shots on every technical decision... Like, bro if this is how you've been operating all these years maybe there's a reason the stack is a complete disaster? Leave the engineering to the engineers, we're here to make business-level decisions and ensure the product works as intended.

Unfortunately, that seems to be the general direction product people took... Glad I'm out


The other extreme (where a product manager on a technical product has zero understanding of the underlying tech) is pretty terrible as well.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: