Heard some great advice recently that I’d like to pass along.

When writing a developer blog there is a tendency to try to be smarter than you are – you follow blogs and read books and you want to make something as good, interesting, and relevant as they are. So you write a couple of drafts and they don’t measure up, so you quit.

The better way to do it is to blog about what you just did. Maybe you ran a standup meeting, or debugged a strange query, or managed to calm down an angry team member. Maybe you ate a good taco while on a conference call. What you just did to someone else might be impressive (depending on the size of the taco) or useful and impressive (calming down a coworker).  You have no way of knowing if what you just did was good, interesting, and relevant to them.