[Tishabet]

Originally Posted by Porsche-O-Phile

Makes sense (I do know something about construction and architecture in particular. . . ). I'm just thinking that long-term it would be much more advantageous to be one of the guys that can DEVELOP software, conceptualize it, figure out what market segments it needs to appeal to, find deficiencies in competing/similar products and meet them (or devise a plan to meet them), etc. than it would be to just be a guy who happens to be good in the programming-language-of-the-month.

Yes, I know that you know something about architecture

I agree that it's more interesting/rewarding to be the guy who can work out the solution to the problem and frame that solution into something that can be built by the actual coders. It's rare to find an experienced software engineer to who doesn't secretly do some architecture work, and it's rare to find an architect who didn't start out as a software engineer.