I've been thinking about some of the software development related habits that I've practiced and acquired over the years. I thought putting some of these down in posts and sharing would both help me solidify my own thinking on the subjects, but also provide a good place to link other developers or anyone I would like to send a topic when the context justifies it.
For this first post, I'd like to highlight some older posts that fit well into this category:
- You are responsible for making that feature work. Write a test. Just do it…
- Segregate your code commits into tiny topical changes
- Leave yourself a breadcrumb for tomorrow.
- Developer humor
- Not a practice - but good to take a step back and laugh a bit...
- rake, psake, grunt, gulp, jake, make, cake, brunch, ant, bash, maven, or fabric. as long as you putOnAHelmet
- One of the Simplest Things You can do to Improve Email Communication
In future posts I'm going to write down some of the habits that I think have helped me become a better developer over the years. While I get glimpses of (being the old guy) in a room of developers, I know that my learning is never done and my future has more personal growth than I can even imagine. Regardless, I hope you find these posts useful.
This article is Part 1 of 11 in a series about Habit of a Solid Developer.
- Part 1 - (current) - Introduction
- Part 2 - Automatically Enforce Project Conventions
- Part 3 - Self Prescribed Code Reviews
- Part 4 - Git Dance
- Part 5 - Update or Add Documentation while Reading Code
- Part 6 - Dig a Little Deeper
- Part 7 - Changes Should be Taken with Baby Steps
- Part 8 - Podcasts
- Part 9 - Rapid Feedback