At Triple Pat, our code is 100% covered by tests. This is an important step towards how we keep our systems reliable and correct, but not for the reasons you might think... Instead, it's due to Al Capone and intellectual forcing functions! triplepat.com/blog/2025/04...

We are assembling a reliable service out of mostly-reliable components (e.g. computers and software). That's tricky to do, and we're very proud of how we do it, how well it's working, and the fact that we do it in public :) triplepat.com/blog/2025/03...

We lint all our Go code pretty strictly. Here's our config, what's yours? What do we do differently? triplepat.com/blog/2025/03...

Triple Pat offers a SaaS service over the Internet, which means the reliability of our service is tied up with the reliability of DNS. Here's how we try and make sure DNS problems don't turn into service outages... triplepat.com/blog/2025/03...

Time is hard to work with when you need to test your code. Injecting a clock can make it much easier! triplepat.com/blog/2025/02...

Reliable system need good metrics, and good metrics require knowledge and thought. Here's the Triple Pat tips for good metric design. We hope you find them useful and use them! triplepat.com/blog/2025/02...

When you `defer` in Go you often accidentally ignore errors. Here's a little trick to make sure you don't ignore things, without having to change your code's logical flow! triplepat.com/blog/2025/02...

Another small function for Go error handling that can make a big difference - LogOnError triplepat.com/blog/2025/01...

"Must()" is a function that has achieved folklore status in the Go community but never settled on "one true implementation". Use Must() and ValueOrDie() to make your code both clearer and more correct! triplepat.com/blog/2025/01...

We're running a SaaS business centered around reliability, so we need to think carefully and be transparent about our dependencies. Writing this caused us to register triplepat.net in order to have multi-provider DNS redundancy between triplepat.net and triplepat.com! triplepat.com/blog/2025/01...

We're building a check-in service, and that comes with a lot of pieces. What technology are we choosing to use, and why? The short version is: we keep it simple, and we choose boring technology whenever possible. triplepat.com/blog/2025/01... It has been working great for us, and we recommend it!

We've added comments to our nascent blog using BlueSky. Thanks @aendra.com for the blue-comments library, it's working great!

Our first post is all about software reliability, and specifically about how we are trying to make our systems reliable. It's not something you can put in at the end - you have to think about this stuff from the start!

Triple Pat just got a blog! Because we like BlueSky, we're going to try to use BlueSky threads as comments. You might see some posts getting created and deleted (both on the blog and here on bsky) as we get this going...

The name Triple Pat comes from how people with pockets often leave their home - right at the threshold, they check "wallet, keys, phone" and do a triple pat. Then they know they are ready to go out.