The story of ReadMe, as told by its founder, Gregory Koberger.

I originally had the idea at the first startup I worked at a long time ago. I had to document their API and a few JS widgets for developers to consume — and it seemed pretty crazy that there wasn’t a simple way to build a developer portal. The concept of which is pretty standardized, yet everyone was spending time building their own, essentially wasting the most precious resource of all, developer time.

I’ve always had an interest in building tools for developers because I believe that usability in software development is sorely lacking. I kept coming back to this problem.

Over the past few years we’ve seen some great examples of companies focus on documentation, and I think it’s great: the faster people learn, understand, and build, the more value is created.

There wasn’t a particular point at which I deliberately sat...

Reflecting back to as recently as a few hours ago, to the equivalent of “that email or message I wrote that could’ve been better”, I feel embarrassed. That feeling alone doesn’t have much particular value; it will do nothing but eat you alive if you let it. However, if you analyze it, treating it like a well-placed sticky note, and ask why you feel that way, you can improve (“Was I overeager? Did I express myself poorly?”) and be more conscious next time.

If you really can’t get a mistake out of your head, acknowledge it (“This was not my best work”). And finally, say sorry — you’ve messed up, but hopefully you’ve learned from it.

A favourite quote, by Bob Hoover, a famous test pilot, goes something like this: Bob had been flying back from an airshow, when both the engines on his plane died. Later, after an emergency landing, he inspected the plane and discovered it had been loaded...