When I was just starting out in the software development world in my early twenties I read a lot of books about my chosen craft. At first I was convinced I was going to be a Windows programmer so I read a lot about C/C++ and the Windows API. I was using Microsoft Access for my day job so I had a few books on Access and learned that product inside and out. I also studied Visual Basic. As I got more into web development, HTML and Perl became big topics for me. Then of course Java came along. I've accumulated more books than I care to admit about Java. I did some non-language-specific reading as well but not much. Mainly
Code Complete and some magazine articles. I was mainly obsessed with learning new languages and technologies. What's kind of ironic is that the language I ended up using the most, PHP, is the least represented in my book collection. The language itself is so easy to use and the online reference so complete no book was really needed. Around the time I built DailyRadar.com (long since dead) I got burnt out on reading about programming languages and software development in general. Sure, I did programming almost everyday as my job but the urge to learn new things slackened. Several years passed without me really getting into anything new. The one exception being that I learned more about XSLT than I really cared to for one particular project. In XSLT I found applications where recursion actually makes perfect sense! But the project I was using XSLT for never saw the light of day and that knowledge has since receded to the darkest corners of the lowest basement of my mind. Getting back to the main topic though. Within the past couple of years I've found the desire in myself again to seek out and consume new knowledge. This time around I'm more interested in general software development methodologies and practices. Things like
design patterns and how to
scale web sites. Maybe this is because I've been around long enough and have been a part of enough projects to have seen what works and what doesn't. I want to learn about other people's experiences with software projects and how we can improve life within this still young profession. It's tougher now to find the time to actually sit down and read and try new things but where there's a will there always a way. Here's a few software development related blogs I've come to read on a daily basis. I highly recommend these to anyone doing programming of any kind out there.
Joel on Software This is required reading. Seriously. Go through the archives and read his past articles. This guy absolutely nails it 99% of the time. The other 1% we'll just chalk to him being crazy every once in a while. His philosophy boils down to two very important things. 1) Be Smart and 2) Get Things Done. I see a lot of people who have one of those traits but the not the other and it always leads to a lot of frustration and failed projects.
Coding Horror This is a recent addition to my list so I don't have a ton to say about it but it seems like a solid blog for programmers.
The Daily WTF Sometimes the best way to learn is by looking at how
not to do things.
Loud Thinking A blog by David Heinemeier Hansson -- the guy who wrote Ruby on Rails. This blog is where I first found confirmation of my belief that people who over-engineer their projects (a.k.a. astronauts) do more harm than good. Does anyone have any other recommendations on good software development related blogs?
Log in to comment