Ghosts In The Wire
Dealing with bugs in imperfect software.
Apr 23rd, 2020 | 1 min read

You've done it.

You closed the last ticket of the sprint. You did all the work you committed to. Everything is deployed to production. Better yet, it's Friday. With the weekend ahead of you, you are feeling the best you've felt all week.

Then it hits.

Your phone lights up like a Christmas tree. It's PagerDuty. You're on call and something is not right in production. Maybe that weekend isn't going to shape up to be as good as you thought it was.


Many of you know, the Bard beta launched week. It's something I'm proud of. We spent a little over six weeks going from idea to creation. We want to help change the way content is created, consumed, and supported on the Internet.

Starting last year, I began developing a finishing-over-starting mindset. That meant shipping more. Iterating more. Unfortunately, shipping fast often comes with another side effect. Bugs.

If you were writing on Bard on day one, you definitely noticed a bug or two. I'm definitely sorry about that. My co-founder is non-technical. Putting something together in six weeks meant a shortcut or two might've been taken.

It's inevitable that bugs will show up in software. Even the most battle tested software has bugs. Even websites like Amazon, a company with something like 3,000 technical staff, develops bugs. They have outages just like the rest of us normies.

I can't promise you that Bard is going to be bug free. Not now. Not ever. But I can promise I'll do my best to fix them when they arise. If you happen to find any, you can let us know online.

Thanks for joining us on this journey. If there is anything we can do for you, let Alain or I know!

This article was written by Anthony Morris.
Consider supporting them so they can create more quality content.