Slashdot Mirror
Coder or Architect?
camusflage queries: "I recently was transitioned into an architectural role by my employer. I had been splitting time with development and architecture, in that order. It appears my new duties put me as an architect first, and a coder second, with the coding being at my request. At not even 28 years old, I'm already a lead developer and have people with twenty years more experience looking to me for coding hints and tips. Over that past year with my employer, I've expended much effort on developing credible relationships with other groups in the organization, sure to carry me far as an architect. Since I've already resolved that management is not a track I want to get into, is architecture my most logical next step? What do I need to do to make sure my skills still remain sharp, as I'll be spending less time in the bits and bytes? Any tips from those who have made the transition from development to architecture (both successfully and unsuccessfully) are appreciated."
Career wise, sure. "Architects" gte paid mreo in many firms.
OTOH I have little respect for Archietcs who don't code (and eys I've done Architect duty). Its too easy to design theoreticly pure stuff that won't work in the real world unless aprt of your brain is actively engaged in "how will I build this" kidns of thoughts.
Pure architects IMO are useless for much more then spewing marekting documents. Keep your hands in the code to soem degree and make celar to management that this is the only way to getr eal value out of you.
Unelss you WANT to become a "Marketecht". Some of those guys get paid very well by large firms, but I dunno how they can loo kthemselevs in the mirror in the morning...