|
I find CTRL+; very handy, I must admit!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I'd prefer one that entered a date of before or after I worked for the company.
Let someone else take the blame for my c**k-ups.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I'm sure it will be super interesting. [Liberal sarcasm].
Regards,
Rob Philpott.
|
|
|
|
|
There is a threat of some previews of current MS development projects that are dev centric rather than a lot of the vapid end-user 'oh look shiny' ballacks.
|
|
|
|
|
bring back t-shirts for us, all 10M of us.
I'd rather be phishing!
|
|
|
|
|
I'll ask 
|
|
|
|
|
Hurry up,
in the meantime someone heard about the gadgets and joined us
|
|
|
|
|
Hi there,
Long time reader, first time poster.
I was wondering what people here think about the various paths we humble developers can/should take. The old stay technical or not debate I guess.
My situation is that I've been a .Net developer for around 7 years and I've now been in my current role for 18 months. During that time I've been responsible for less and less .Net code and instead been given more team and project management responsibilities.
There are various analysis and design elements to my job and the team and project management parts are certainly new skills which I'm finding interesting, but I'm still unsure if this is a good route to go down or if I should keep myself more technical?
I'm interested in any thoughts on these paths, and whether there is a difference in their value at different ages/stages of career?
|
|
|
|
|
Go with the role that makes you happy. I tried being a manager once and hated every moment of it. Once I got back into a technical role my job satisfaction rose exponentially. But I know managers who relished every aspect of their job. It's horses for courses.
|
|
|
|
|
As Richard said, I moved away from coding but found it less stimulating and I am ow actively trying to move back that way. Not 9-5 code monkey stuff but a good balance between tech and human systems.
|
|
|
|
|
I loathe managment; not the managers, but the actual duties.
You have to decide whether you prefer design and development, or management.
I am an Engineer that has turned down management oppurtunities many times. I even make it known that I have no ambitions to be a manager, if asked during interviews or after employment.
Good luck.
|
|
|
|
|
I can't say anything about long time experience, cause i'm working as a "Developer" for only 2 years now, mostly coding, but on my specifications (solo-project).
But i'd recommend to stick to whatever you feel like, the best paid job is not worth the struggle you have if you don't like it.
If you are interested in moving up to project management then do it, a projectmanager able to code is worth far more than one only having experience in managing (my opinion).
If you prefer coding and the responsibilities behind that you should consider staying technical.
I for my self like coding, but i really like developing software architecture and managing what's up to do and needs to get done. I could never be a programmer who is writing code without having the possibility to get a view of the whole project, thats why i would not stay too technical.
Simple thing i often remind my self, do what you like to and have fun with it, you'll do it a lifetime.
Stay true to yourself and you'll make the right decision 
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
perhaps being an architect is more up your alley ?
|
|
|
|
|
"Career" (verb) - to go downhill in a rapid and uncontrolled manner.
|
|
|
|
|
I was not skilled enough to go on the technical path, so I turned to management.
I'd go back anytime to development - would the paycheck be the same. 
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Entropy isn't what it used to.
|
|
|
|
|
As some have stated. Been down the management path, it is interesting but I do enjoy programming. Right now I am a team lead without any reporting responsibilities. So I don't do the reviews. IF they come in late I don't care. If their code sucks then we have a discussion. I like it. Works for me.
And there is the crux of the deal. Find what works for you. It might be different in differing departments and/or companies. The surrounding personalities and abilities often drive people to differing roles just to get the product out the door.
If you are ending up doing PM duties it is probably because there is a vacuum there and it needs to get done. If you are enjoying it and not hating the job. Keep at it. Be flexible. Keep your skills up always though.
To err is human to really mess up you need a computer
|
|
|
|
|
As others have said, go for happiness over other considerations, it really will pay off in the long run.
Personally, I'm a developer. Sometimes, this means being a technical team leader, or systems architect, and that's fine. I'm staying away from project and people management, though. I've tried it and don't like it.
If you are in management, you can screw up people, who are harder to repair and roll back to previous versions than software is. This responsibility can weigh heavy on some managers. Which type of role has the most pressure and stress overall depends entirely on the organisation you are in, and its culture. Salaries and perks also vary - I've worked at places where non-technical project managers have had lower salaries than the developers. In other places, you have to become a manager to get higher salaries.
Don't be afraid to try out a challenging role that looks interesting, as long as you're not afraid to say "No, this was not for me". That is much better than moping about opportunities not taken, or staying in a role you are unhappy with to 'save face'.
|
|
|
|
|
It's a choice...
Become a manager = More money, and instead of building things, you tell other people to build things. You're not a programmer anymore.
Stay as a developer = Less money, but you get to keep building things.
So it depends on which is more important to you... More money is nice, but I'm never going into management.
|
|
|
|
|
Management is nice if you like it - it is like you are in control of the team; I have seen people micro-manage, and that is not liked by the subordinates.
One thing I dislike about management is the evaluation part at the end of the appraisal period. Writing good things is OK; but if there are points for improvement, there is some creativity involved in writing them in a diplomatic way. Giving bad feedback is definitely not easy (at least, for me).
On a slightly longer note, I've heard of the four stages of an engineer:
Stage 1: Is a student of engineering, learns how science is made to work for doing useful things to the human-kind.
Stage 2: Joins the first job, learns the nuances of the trade by working with/under seniors. This stage lasts for about 10 - 15 years. Towards the end of this period, he knows a lot of technical stuff.
Stage 3: Gets into the supervisory role, and guides others/juniors to do their tasks. This stage lasts for 10-12 more years. Gradually this person increases focus towards management, business growth, etc, and simultaneously loses touch of technical details.
Stage 4: Finds himself so far away from technology that he starts developing / growing interest in fine arts, music, drama, and other humanities-oriented aspects of life. Prepares for retirement. This stage lasts for <<...???...>> years.
This is perhaps true even today.
|
|
|
|
|
I've been on both sides of the fence, and in my current gig I'm doing 90% management, 10% coding.
Project management is an excellent skill to have in your toolbox. It's highly transferable and makes you stand out from the rest of the folks who "just write code".
Try it out for a while, see how it goes. Try to get some mentoring, perhaps some PM training/classes. If you don't like it you can always go back. I know a lot of people who were never happy in management, which is fine. It's not for everyone.
From my experience, I've been moving away from active code writing over the past few years towards management. It's been a lot of work but I get to work on the business side which often has tougher problems than writing the code. You get to deal with different problems.
"Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music."
-- Marcus Brigstocke, British Comedian
|
|
|
|
|
SirFoxworth wrote: Trajectory
Similar to what Duncan Edwards Jones said:
Something about "Trajectory" makes me think it's bound to go down hill and slam into something solid, perhaps with an impressive explosion.
|
|
|
|
|
SirFoxworth wrote: I'm interested in any thoughts on these paths, and whether there is a difference in their value at different ages/stages of career?
Becoming a salesman and just that is something that is economically rewarding and professionally if your mind goes that way.
Otherwise it is all just technical and a business analyst tends to become more industry specific especially with more skill versus a developer so don't do it (if one wants to weigh the pluses minuses) unless the industry is broad enough.
|
|
|
|
|
As you have probably noticed, most developers try management at some time in their career, some like it and others of us can't wait to get back to coding.
YOU are the one who needs to try it, a good manager with a technical background can be a huge asset. A lousy manager is just a PITA. However it can be a challenge moving back from PM/BA/Manager to a developer role.
Another thing is imagine a 60yo developer trying to get a contract/gig in today's or any market, some of us are in that position!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
SirFoxworth wrote: whether there is a difference in their value at different ages/stages of career?
As in: will different skills have more or less value to me and/or my employer at different stages in my career?
Depends if the skills match up to what's needed at a given point in your career, or if a given skill will allow you to move to a new stage in your career.
Exposing the brain to new challenges is always, always good. At the most basic it ensures mental flexibility and can give you new thoughts on old problems. At best you may stumble onto something you find you really enjoy and you're really good at.
cheers
Chris Maunder
|
|
|
|
|
Seeing as the ink-pedlar-in-chief hasn't posted in nearly a month:
Sight-seer? (8)
Alberto Brandolini: The amount of energy necessary to refute bullshit is an order of magnitude bigger than to produce it.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
