First, they might be deterred by the issues I mentioned in the post. None of the challenges I mentioned in the piece were special. We lost a customer. We had an outage (a year ago). We were stressed. Every API company and competitor, not to mention our customers, have had a similar story. Of course we made it through those challenges, or we wouldn't be telling this story. They made us stronger. Plus, we love it when prospects ask about uptime because it's something we take seriously and where we have a great track record :)
Second, they might be deterred at the idea of failure being ok. Perhaps the message in the piece is too subtle. It's not supposed to be that it's ok to be lazy and fail at stuff. It's about getting perspective and not letting your anxiety cripple you. I hoped what would come through in this piece is that we care very deeply about our work, so much so that sometimes we needed to be reminded that it's not life or death.
Finally, I'll share some of my thoughts on why it might be beneficial to share.
First, like I mentioned in the post, being a part of the tech community and contributing to it, sharing some of the lessons you've learned, is very rewarding. I've found that when you give, not only does it feel good, but the community gives back, often later on and in surprising ways you didn't expect. You reach like-minded customers, partners, candidates, investors, all kinds of things.
Second, as a data company, trust is incredibly important to our brand. Some might disagree, but I think sharing the more human sides of the company helps to expand that trust. This is how we have always operated the company, and I think it is a large part of why we not only have a lot of customers (and growing), but many fans. We like knowing our customers and we like them to know us too.