Developing a better developer

I find that I learn development by doing, doing wrong, then fixing, then learning a better way. One example is the use of master pages on my web site. I wanted to learn the new technology, break it, fix it, then figure out a better way. I think that’s why I do so many different prototypes and always seem to have 3-4 pet projects on the go.

JP Boodhoo has posted two of the best posts I have read regarding improving yourself as a developer:
 The real crux of the quest, as I see it, having both discipline and passion. Scott Hanselman‘s recent podcast about Hiring and Interviewing Engineers hit it on the head. You just can’t teach height.
One question I have been asked is what books/resources should a developer use/read to improve. I would put them in this order:

I’d be really interested in seeing other people’s lists. There are tonnes of good developer books/resources out there I haven’t read and the budget for books is looking good this year.


One thought on “Developing a better developer

  1. Totally agree. Don’t be afraid to break stuff. Fixing broken things is one of the best ways to learn.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s