[brd]

I absolutely agree that going for an architect role is the solution to this problem. The key to becoming a successful generalist is to learn how to bring technologies together. If you can paint the picture of how integrate different systems/tools/languages/teams/etc then you have a very valuable skill to an organization. Unfortunately this means not just being good with technology but also being good with creating or refining specs, understanding business processes, juggling priorities, and all the other good stuff that is needed to handle complexity in the work place.

[alok-g]

Thanks for these inputs. :-)

Of all the things you mention for complexity in the workplace, the hardest I find is understanding business processes since they are often industry-specific (specialized) themselves.