3 ms·

I am sure you did not intend it, but the "chef to waiter" statement is such a big disservice to what solution architect people do. Using your analogy I also cer

I am sure you did not intend it, but the "chef to waiter" statement is such a big disservice to what solution architect people do. Using your analogy I also certainly don't believe that writing code equates to being the chef. I love software development and see the tremendous value it brings but in most major businesses its relegated as a cost centre rather than revenue generator. I don't equate being in a solution architect role to not writing any code or being a bad developer. It actually takes a much broader skill set to do a solution architect's role. The best solution architects have reasonably high communication skills, strong understanding of business drivers and are able to articulate well to non technical people and most important see technology as one cog in a business rather the be all and end all. These are not skills that any typical developer will necessarily have. The term is also abused a little bit but in major corporations it has a lot of weight. I would also say that just like any role, there are the best and worst people doing it. The reason I mentioned it is that for people who still have a strong love for technology but don't want to be relegated to being a developer when they are much, much older (and frankly who want more advancement) the solution/enterprise architect seems to be a good fit.

peacemaker 13y ago
You have a good point about those who want more advancement moving into roles like a solution architect. For me, I'd prefer to stick to development as this helps my side projects and potential businesses more. Then again, if I moved "up the ladder" as it were, there may be more opportunities I'm simply unaware of as a developer? Thanks for your insight.
givehimagun 13y ago
Chef to waiter isn't a good analogy in terms of skills. I was trying to highlight how different the roles were and not the skillset disparity. Hell, I'm one of them...my job title is application/solution architect and I spend most of my time doing exactly what you said above. I agree with what you're saying. My main point is that what I've seen (and even heard from people I'm interviewing) is that they want to become an architect to move away from code and graduate into another position. I think your point of needing a broader skill set is important because in my mind, architects are excellent at their old job, continue to do portions of that job and also gain the other skills (communication, change management, evangelizing)...but I don't see everyone understanding that.

peacemaker 13y ago

You have a good point about those who want more advancement moving into roles like a solution architect. For me, I'd prefer to stick to development as this helps my side projects and potential businesses more. Then again, if I moved "up the ladder" as it were, there may be more opportunities I'm simply unaware of as a developer? Thanks for your insight.

givehimagun 13y ago

Chef to waiter isn't a good analogy in terms of skills. I was trying to highlight how different the roles were and not the skillset disparity. Hell, I'm one of them...my job title is application/solution architect and I spend most of my time doing exactly what you said above. I agree with what you're saying. My main point is that what I've seen (and even heard from people I'm interviewing) is that they want to become an architect to move away from code and graduate into another position. I think your point of needing a broader skill set is important because in my mind, architects are excellent at their old job, continue to do portions of that job and also gain the other skills (communication, change management, evangelizing)...but I don't see everyone understanding that.