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."

5 of 405 comments (clear)

  1. Mod up ^ The one thing you cannot lose: control by moogla · · Score: 0, Redundant

    The most important point made here: Stand your ground and don't let yourself become slaved to the project management.

    You will find yourself in a unique situation, with one foot in engineering, and the other in management. As a result, you will become management's favorite go-to guy. Similarly, the engineers that you work with will also try to use you to influence the decisions of the managers. Be fair and responsive, but don't feel you need to cater to everyone's whims.

    You will have to a little delegation, but don't it let monopolize your real job. Commit yourself to planning and writing code, and just being productive. You will not lose touch with your skills in this way.

    --
    Black holes are where the Matrix raised SIGFPE
  2. Youza Nerd-to-PHB translator by Tablizer · · Score: 0, Redundant

    (quote) High-level engineers are often depended on by managers above them to translate engineering concepts. This can drive you nuts as you realize how little some managers know. (end quote)

    Once I was trying to explain why it is tough to get computers to guess at typos and try to match mistyped car license plate numbers as well as guessing humans, and the manager suddenly stepped out of the room and whistled to my supervisor ("systems architect", et al) to come over and translate my alleged nerd-speak. It was like, "Just a second, Yo! Translator, over here!"

    I eventually did make a Guess-A-Tron, but they did not want the results anymore by then. But, it was a fun project.

  3. duh ... by halftrack · · Score: 0, Redundant

    Developers: Coder or Architect?

    Can you be an architect without being a coder? Don't think so.

    Seriously, an architect is just an upgraded coder. Fatter pay-check, fatter office and fatter slave-staff (not reffering to MacDonald coders.)

    --
    Look a monkey!
  4. IMHO by catseye_95051 · · Score: 1, Redundant

    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...

  5. Lets see your resume first by androidbug · · Score: 0, Redundant

    Let me see your resume first, then I will try to give you some hints on becoming a succesful software architect.