It was the same, shitty experience it’s always been.

Xitter has quite the ring to it.

Wouldn’t be the first time.

Also yes.

For sure, in PCI environments this doesn’t work. And in the Series F company we don’t use this approach for that very reason. But there’s tons of companies that don’t have or need external certifications, and it works for that much more common scenario. For the small web (i.e. most of the web), it’s ideal.

The important takeaway isn’t “wow, doing production builds on your PC isn’t secure.” Do it on a dedicated box in production, then. The important takeaway is there’s a mountain of slow things (GitHub workers, docker caching, etc) which slow developer velocity, and we should design systems and processes which remove or eliminate those pains.

Hi friend, this was just meant to be an introduction, as I get started blogging and sharing back some knowledge and lessons I learned along the way. I’ve never written a blog before (or much of anything!), and I’m sorry you didn’t find value in this.

I wasn’t intending to boast, but I can see how it came across. I just meant to say, “companies are trying to tell you that you need ‘XYZ’ to scale,” and at least at the size of business I ran, you didn’t need any fancy tech at all – we could have made do with a dead-simple setup: a single server running Go and SQLite. It’s something I wish I had known when I started.

I’ll take your feedback to heart and try to produce larger, more substantial posts to follow. Thanks for commenting.

I’m concerned that your preferred solutions may ignore the needs of working with peers. When I’ve worked with similar solutions before, we had a lot of on call, and it all went to the same person, regardless of who actually answered the phone.

Totally hear you and have the same experience myself. The approach I’m advocating for is simply running a binary on a server with rsync to deploy, and architecting your product around that limitation. Teaching a team the basics of Linux sysadmin will be incredibly useful for their careers, and it’s something that the whole team can easily learn. Then you don’t need to hire a k8s team – any engineer can do some basic debugging when things go sideways.

Fair criticism. I wanted to lay the groundwork as I intend for it to be a pretty large resource for people over time. Like starting with chapter one before I write the whole book. I hope you can find some value in some of the stuff to come.

Writing the second post now :-)

Only just started using it, but I love it. Simple, basic blogging without the enshittification of Medium.

Is it too late for, “I use nix btw”? I use it at home and for development.

I planned to focus this blog series on ol’ faithful (Debian), but I could definitely see writing articles on how to use Nix and OpenBSD if people find it helpful.

Brave itself is filled with ads. Crypto wallets, BAT, VPNs. I just want a browser.

This breaks my heart.

To be fair, that includes a large popcorn.

Bird. Birdy Birdy.

100%. I also like to leave comments on bug fixes. Generally the more difficult the fix was to find, the longer the comment. On a couple gnarly ones we have multiple paragraphs of explanation for a single line of code.

That is 100% how it should work. No taxation without representation.

They have a concept of a plan to federate.

ooooooh