Can you think of a more boring title than that???
When I slip in my blogging frequency it is almost always due to a focus on work and the need to meet project objectives. I almost never have to code to deadlines, but I know what I need to accomplish today, or this week, or in some cases, this month, to know that I'm earning my paycheck. The guys who sign my paycheck might not know that I took until Thursday to complete a task that I had planned on Monday to have completed by Wednesday, but _I_ would know, and that is what matters. Sometimes unforseen issues arise and things take longer. Sometimes things are just hard and we need more time than we thought we needed. But we can still try to squeeze out the productivity from the week we were hoping for going into it, and in doing so blogging frequency can sometimes drop. And hell, that's okay and a nerd has to live with that.
It's an interesting cycle: can't blog because you need to meet work objectives; while hustling to meet work objectives you discover new and better coding practices you want to blog about. I make a quick list of code points during those times, and will typically go back to them when a blogging window again opens up.
The main thing to be thankful for is being in a position to discover new and better ways to write code. Blogging about them is the icing.