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."
Code Free Software in your spare time!
And don't let yourself get sucked into project design/managemnet, which would defeat the purpose.
-Peter
I originally started as a programmer in college (ok, first was the track for electrical engineer, but alas, calc II killed my plans less than kindly) and touched on some of the aspects of design, development and some of the "herding cats" aspect of project management.
I'll be the first to admit that I did not have the stamina to code for a living, which lessened my interest in doing so. Like anything of interest, it is a slow learning process.
For me it was a slow degradation of the fun aspect of programming. The thrill is still there, but, the hard work of programming just kind of wore me thin (figuratively speaking, of course...literally, wellll, lets not talk about it).
As a "Lead Developer" for your company, you have both my admiration and my condolences.
My condolences, because it is always hard breaking away (or being forced away) from your "first love", so to speak.
My admiration, for you are moving up and are getting the realization that it is a needed step.
Here is the thing that may or may not hit you sooner or later, as it has happened to me on a couple of occasions: the people "under" you are better than you at coding, more often than not.
It is a harsh reality to face, but here is the kicker: Yes, your underlings are better at coding, but not at design and architecture! Hence, your position is more important than you think. To put out to you the words of wisdom/cliche, "those that know how, will always work for those that know why".
Think about it, really. Your role is more of a teacher, guru, advisor or sensi (SP?).
You've been there, done that and you've got the experience of the big picture that those you work with need.
I know first hand from working with coders, techs, IT, MIS people that are so sharp they could have my job in a heart beat, but, invariably I find the one thing they are missing is the why. As a matter of fact, one particullarly sharp individual thanked me saying "in school they tell you how without explaining the when, where, and why it is done in the process".
You have to see that you are in a unique position of taking the fear and uncertainty and doubt out of the the process of development and coding.
At the risk of sounding very silly, it is quite a "Zen" feeling, because you have to let go and move up in order to be the best person for the job.
I think physiclly, you are there, the reality has yet to catch up to you.
FWIW, naturally.
Have you read the moderator guidelines? Well, have you, PUNK? (and I want a Karma: Gnarly option)
Exactly 2 cents worth, you corporate monger.
There's nothing wrong with corporations, but as
many here fail to see, most computer companies
fail, because they are organized with wrong
structure in mind. Companies build products, on
single request of head person. Basically a request
comes in and so the project begins. In
present structure, decisions are made high above
people, such as taking out that button, or taking
this screen away and moving it here. There's
not consultancy with people who will receive the
end products, because they are considered consumers,
dumb and not knowing what they want.
Company shall provide consumers with service - thats not what most do. They build software,
and shove it down customer's throat.
Furthermore - programmers, are seen as a cement
mixers - ones who just need to know how to type,
and they will make something. Programmers are of
least importance in corporate structure.
People come from other places and expect
programmers to be like factory workers or
journalists - make a volume, and you will be
qualified for high salary.
It's a nightmare. Its like everyone is confused,
in denial on what needs to be done, or even
does not know what needs to be done, so they
make it up!!!
Way to eliminate problems as earlier poster said
is way of XP. Where managers are merely communication
inducers. Customers are responsible for vision
of the project. And coders are responsible
for making of the code. This way projects
are grown, they are never wrong, and if they are,
that can be easely adjusted on early stages.
In most companies focus is wrong - they try to
get everything done and make a shiny thing for
customer, whike XP makes software for customer
that fits them, and maybe not as shiny but more
natural. Architects role therefor is wrong for
99% of the software projects. Customers
shall decide what should go into project and
what should not. They pay by hour for development,
so they shall control it as that, and so they shall
be responsible for results.
Being Architech is partaking in process full of
psychological illensses that are hampering this
industry since the dawn of time. If you wish
perpetuate that, do proceed with going up.Otherwise
start looking for small companies that will listen
to you as an expert. Start by reading XP series
books.
http://www.extremeprogramming.org/
Dear Slashdot,
I think I am super hot shit. All these old programmer nerds are looking up to me. I'm like, not even thirty, and I'm obviously successful as hell. Sexy too. My question is, how can I inflate my ego more?
Ah, the irrational and instinctive belitting of a person who makes a valid point that you disagree with. I'd say you're ready for management.
This is a troll. Do you see the difference?
If you were blocking sigs, you wouldn't have to read this.