Knowing When You’re Tired
There's a big difference between code you write when you're fresh and code you write when you've just had enough. I obviously had a relaxing weekend, because today my approach to coding was surprisingly well behaved - even when I had to modify legacy code that had no test coverage I made sure I wrote new tests before I touched it. Getting into TDD for new code is one thing, building up the discipline to add tests to existing code before making even a simple change is really tough.
Fortunately, if you know you're getting lazy you can manage it either by paying more attention to the process and taking smaller steps or by doing something simpler that requires less concentration. The real danger is when you aren't aware that you're fading out and taking shortcuts - that's where you really need a pair to step in and pull you up.
March 22nd, 2006 at 12:37 am
“Fortunately, if you know you’re getting [tired] you can manage it either by paying more attention to the process and taking smaller steps or by doing something simpler that requires less concentration.”
Man, that is timeless advice. As a developer I hear you but I’ve found myself using that pattern in all aspects of my life. I do a lot of 24+ hour motorcycle rides, that strategy is the key to getting through the midnight to 6am timeperiod succesfully.
Maybe I should use the “sleep more” pattern instead, but who has time for that :)