News for hackers. Stuff that matters.
Re:Ask HN: How to plan your career for an Architect role? by ChuckMcM on Tuesday August 25, 2015 @10:45AM (#10116857)
I'd echo some of the other answers here, what do you think "architect" means? And then ask what could you do as an architect that you can't do as a developer?

There are places like IBM and Oracle where they have specific job functions defined for the architect role (and training to get you there) so if their idea meets your idea you would do well to just work for a company that trains for that role.

There are also people who have a lot of experience who are sometimes called "architect" but that is a function of how much experience they have, which really you can't push faster than the passage of time. You spend all your days working on the technology and encounter many different situations and then 10 to 15 years later people start thinking of you as an expert/architect.

There are developers who have better design sense. I don't know if that is a talent thing or just that they pay attention to not only what their code is doing but the structure of it and the underlying problems it solves. People will experience their code not only solving the problem but anticipating future problems and either handling them or having a clear evolutionary path to handle them. They start being called architects at some point in their career.

So why do you want to be an architect?

There are no comments on this comment yet.