I just read this post from Justin Etheredge about strategies for becoming a better developer:

CodeThinked | What is your strategy for becoming a better developer?

Self improvement and mentoring others to improve is one of my strongest passions right now.  I think that Justin's two recommendations would also be my first recommendations for being a better developer.  These are "Emulate" and "Get Involved".  I'd also like to add "Read" and "Stretch".

Read.  This pertains to blogs, articles, and books.  Subscribe to RSS feeds, magazines and commit to a reading list.  These resources are extremely valuable in extending your breadth and depth in a particular technology.  I commit at least 1 hour of my day to reading interesting things.  Most of the time, they have nothing to do with my exact job at hand but at the very least gives me perspective into successful people's habits.  CodeThinked is one of over 100 blogs that I subscribe to.  One tip here: Actually SUBSCRIBE!  Here are some instructions by Jeff Blankenburg.  This will create a virtual Todo list that you can follow.  If you don't subscribe it's very easy to let your day job get in the way of investing in your profession. 

Stretch. By this I mean set goals that push the limits of your comfort.  One area of comfort that I was not ready to move into yet was speaking publicly.  When I was younger, I had a severe stuttering problem.  It was difficult for me to hold conversations with people; even those close to me.  Through two years of speech therapy sessions and some significant confidence boosting activities, I overcame that shortcoming and was able to hold conversations and even group discussions occasionally.  It was a big stretch goal of mine to give a public presentation a few weeks ago at the Kentucky Day of .Net.  But it was an enormous growth experience.  Find those things that you have no comfort with and become comfortable.  Specific to programming: if you are a .Net developer, check out f# and become proficient.  Learn some Ruby well enough to share it with others. 

Continue this list of recommendations and extend Justin Etheredge's non-meme.

 


Posted in:   Tags:

Comments


 Sam
September 22. 2008 16:44
Sam
I could never handle 100 blogs! I like your suggestion to Read. I don't know much about F#. If I was school I would rather get a C# than a F#.

http://dotnetperls.com/http://dotnetperls.com/


September 22. 2008 20:30
Rick
@Sam,  The 100 blogs do take some time.  Here's a tip: if the blog doesn't catch your attention after 45 seconds of reading, don't read the rest.  I don't spend much time every day reading blogs, just a few minutes in the morning and then a few at lunch and then a few before I go home for the day.  I tend to keep up.  

http://rickdoes.net/http://rickdoes.net/


September 22. 2008 21:10
Troy DeMonbreun
"Non-meme"... heheh

BTW, kudos on public speaking despite a history of stuttering.

http://blog.troyd.net/http://blog.troyd.net/


September 30. 2008 13:23
Jeremy Thake
I completely agree, I have over a 100 blogs I subscribe to and social book mark them using diigo for reference. I tend to blast them every evening, they do build up though! and I'm always adding more and more and have got to the point of ranking them based on how many I actually bookmark etc. It can get hard to keep up with the community being so enthusiastic!

http://wss.made4the.net/http://wss.made4the.net/


 An Phu
November 24. 2008 22:05
An Phu
I would add participation in the msdn forums.  Not only does it reinforces what you know but is a useful learning tool.


no site

Comments are closed
Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2010 Rick.Brain.Flush()