Status

What I’ve learned so far about consulting work: Harvest feeds the OCD time tracker inside of me. Creating proposals is a huge time suck. There’s so much room for automating all of this.

Status

Couple of things I learned the hard way yesterday: When using a password to connect to an IRC server, you’ll need to join the room before you can post a message to it. IRC servers (or maybe it’s just ours) are quite slow to fully respond to connection requests. Like, two minutes slow.

Advantages of code review

Advantages of pre-deploy code review, over post-deploy audit: Authors have a strong incentive to craft small, well-formed changes that will be readily understood, to explain them adequately, and to provide appropriate test plans, test coverage and context. Reviewers have a real opportunity to make significant suggestions about architecture or approach in review. These suggestions are […]

Matt Haughey’s lessons from a 40 year old

I like to think of funded startups vs. bootstrapped web sites like the split between signed and unsigned bands. Think about what a band has to do if they sign with a major label. They write music, perform/record it, and play it. Now think about people like Prince, Aimee Mann, etc. that do every single […]

What makes a good commit message

There’s a useful conversation happening in an internal Automattic P2 I thought I’d take the liberty to share. From Mike: Consider the audience when you write a commit message. What is that audience? It’s at least two groups of people: Your coworkers: You’re telling everyone else what you did. Commit messages are one to many, […]

Writing beginner level tutorials

Writing beginner level tutorials. A number of useful tips. My favorite: “use words and phrases that your reader can Google to find more information.” For producers of documentation, I think the biggest challenge is putting yourself in the mindset of the reader. The second biggest challenge is closing the feedback loop between the person who […]