Code-First Reliability: 4 Unconventional Approaches to Always-on Payments
Today is the launch of my newest book, titled Code-First Reliability.
Paid subscribers can get it for free until the end of August by clicking on the link at the end of this article. Free subscribers can get it for $24.99 via this link, or by becoming a paid subscriber for $20 a month.
There are at least two modes for running a newsletter. One is with a focus on distribution, the other with a focus on advancing the industry.
When a newsletter is focused on distribution, what matters is entertainment. This mode follows the news-worthy and the trendy, like the guy who was hired by 10 startups at the same time, or the unfaithful tech CEO. It offers lessons from the coolest companies about problems you don't have. And it currently talks a lot, A LOT, about AI.
The Payments Engineer Playbook is focused on advancing the industry.
When a newsletter is focused on advancing the industry, what matters is value. This mode contains articles that can be placed only in three buckets:
First, purpose. Advancing the industry can only happen when those who have been hired to do the job understand why they’re doing it, and can come up with new ways to make it better.
Second, context. Once you know what is the purpose of your job, you need to know how to do it well, what kind of boundaries exist that put limitations on what you can and cannot do, and what kind of tradeoffs you have to engage in.
And third, technique. Having clarified why your job exists, and what are the rules of the game, the only question that remains is “how do I win this game?”.
Readers of newsletters focused on distribution get entertained. Readers of newsletters focused on advancing the industry get better.
A good friend of mine, who’s also a subscriber of The Playbook, once told me that the newsletter should be able to reach as many ambitious and driven payments engineers as possible, and ignore the rest.
For them, today, I introduce Code-First Reliability: 4 Unconventional Approaches to Always-on Payments.
Over the past few weeks, I’ve published a few articles dedicated to the practice of keeping payment systems running. The feedback has been tremendously encouraging, and I’ve decided to package it in a format suitable for the ambitious and driven engineers who aren’t paid subscribers.
I want you to advance the payments engineer industry. And I want you to have the tools to do it well.
Code-First Reliability consolidates the insights from multiple articles of The Playbook into one coherent book, rewritten almost completely to ensure that, when you put it down, you’ll think to yourself “that was a great use of my time”.
In fact, you can read the first chapter for free here:
If you’re not a paid subscriber, you can purchase Code-First Reliability for $24.99 by clicking on this button below.
But let me suggest something better.
You can instead subscribe to The Payments Engineer Playbook. That way, you can have the book for only $20, plus access to all the articles in the archive, including Payments Patterns: Elements of Reusable Money Software, 3 Ways You Can Improve Your Payments Authorization Rate Right Now and The Best Payments Database Is the One You Aren't Using.
And then, after a month, you can decide if being a paid subscriber is worth it. I’m confident that you will.
If you’re a paid subscriber, you can get your copy of Code-First Reliability, for free, on the link below, until the 31st of August: