Software-development

If your career is anything like mine, you've dealt with a wide array of various code bases across multiple technologies. Some web, some client, etc. With varying technologies, the tools change, the languages change, everything changes. A few things have remained relatively constant, though, such as a command line.

Last week, prior to a weekly meeting, one of my team members had the idea to take a few minutes before the meeting to review some code. We already do code reviews prior to deployments, but we've been wanting to improve the quality of the code reviews... we wanted to really have good dialog about code quality and be able to share that discussion with the whole team.

This post is about, well, how I got started in programming. Yep.

In my post looking forward to 2008, I mentioned that I wanted to take more time this year to learn new technologies, particularly outside of the Microsoft communities. With all of the push in .NET towards dynamic languages right now, why not look to some of the dynamic languages that have been out there being used for years?

Be proud of your code, even if you wrote it the wrong way... consider it a learning experience.

Reflecting on posts from the ALT.NET conference

In the few years that I've worked as a software developer, I've read and seen many examples of testing software. As a result, my own thinking regarding testing has changed drastically over the past year or two. It seems that there is a continuum behind the thinking that goes behind testing. I originally titled this post "the Evolution of Testing Thought Processes" but evolution doesn't describe this as well for me, because I find myself moving between the different processes depending on the circumstances.

I have so many books I need to read right now, it isn't even funny. In my office at home, I've got about 8+ books which I need to read, and the majority haven't even been started yet.

Reflections on going through the Classic Mistakes survey