Asking good questions is a super important skill when writing software. I’ve gotten way better at it over the years (to the extent that it’s something my coworkers comment on a lot). Here are a few guidelines that have worked well for me!

After using Git for several years, I found myself gradually using more and more advanced Git commands as part of my daily workflow. Soon after I discovered Git rebase, I quickly incorporated it into my daily workflow. Those who are familiar with rebasing know how powerful a tool it is, and how tempting it is to use it all the time. However, I soon discovered that rebasing presents some challenges that are not obvious when you first start doing it. Before presenting them, I’ll quickly recap the differences between merging and rebasing.

I wasn’t going to write this list. I wasn’t going to, but then I mentioned it, half-joking, in the Literary Hub office. Turns out everyone was extremely excited about finding out how tall their favorite writers were (or are). Who knew, right? Anyway, I decided to do it after all. Because it is fun. If you don’t think it’s fun, well, I don’t have to explain my art to you.

A peculiar challenge of management is trying to invest in someone's career development when they themselves are uncertain about their goals. As a manager, you may have more experience and more access to opportunities within the company, but that represents a small slice of someone's career possibilities. Our schooling often rewards us for being methodical, linear thinkers, but that approach is less effective outside the intentionally constrained possibility spaces.

Here’s a funny thing about work: We spend more time with our colleagues than with our friends and family. Yet more often than not, we don’t really understand our co-workers—because being honest with one another is scary.