3 ms·

I'm main Architect in my current company now. And I hate this title - I've seen too many so-called architects who can't distinguish SOAP-call and MQ-message.

• aik 14y ago
  I don't think this is for your point, but here's a counter-example: A large company uses 100 widely different technologies, and obviously no one can be an expert or even slightly knowledgeable about all of them. However when you're a SOFTWARE ARCHITECT [oooh!] it seems like there's an expectation that you should be an expert at everything. As soon as you're not (e.g. your example), you're seen as incompetent. In this case there's an unfair expectation.
  • Ingaz 14y ago
    Of course. But 100 really widely different technologies is A LOT. My specialization - telecom industry. I'm dealing with families of technologies and they are not so plentiful. Messaging is messaging, DB is DB, application servers are application servers. Backoffice-frontoffice-mediation-billing remains the same in essence even if you change every component. I think that I can become good (after 2-3 years) in banking software or manufacturing. I think it almost impossible for me to become proficient in something like game production, high performance computing, many others