No hanging chads here, we promise! Login and vote now.
By mswatcher
via andrewtokeley.net
Published: Apr 16 2008 / 11:11
Hopefully most will have actually considered the change of role and be looking for new challenges and ways to contribute more to their chosen profession. However, for some this is an automatic response to a question that is particularly difficult to answer in an industry with no clear career path. For others it's simply a way to move up the pay scale.
-
Авто
-
On Google’s Chrome and The Future of Cloud Computing
-
Avoid NoMemoryError during model reindex with ferret in ruby on rails
-
DataDirect Technologies Announces Version 4.0 of its Industry-Leading JDBC Database Drivers
-
GridGain - simple, effective, and made of pure happy juice
-
Firebird is faster than the filesystem for blog storage
Comments
Tushar Joshi replied ago:
I found this article thought provoking.
julian doherty replied ago:
Good advice for anyone who wants to be a team lead, but hasn't really thought about why. I did my team leader stint, got sick of it, and am now back to senior dev. Much happier now just being able to code and not deal with all the other stuff.
willcode4beer replied ago:
One thing to keep in mind is how the role gets pushed onto developers.
Many feel pressured to take the role, especially when asked during interviews, "with all your experience, why aren't you a lead yet?".
Others have it pushed on by management, who generally think they are rewarding someone for a good job. It can be hard for many developers to turn it down.
Now, I'm in the role, even though I don't get to code quite as much, I do get to place a higher emphasis on quality, by spending time on it, and through mentoring other developers.
Voters For This Link (25)
Voters Against This Link (0)