Blake Smith

create. code. learn.

»

Hello RWX

After 11 years engineering and building the business at Sprout Social, I’m excited to start my next adventure.

I’m joining the engineering team at RWX!

RWX Logo

The RWX team is laser focused on making Continuous Integration services a joy to use again. LLM driven coding has forced engineering teams to rethink how they integrate feedback loops into their development cycle, and RWX has the product and technical underpinnings to accelerate creative feedback loops for software teams. The first rule of any creative process is to make sure your feedback loops are tight, and RWX has this foundation in spades.

My career has always focused on building deep, distributed systems, and it’s an exciting time to work on infrastructure products with a small, high velocity team. There are endless opportunities to reimagine parts of our software stack, and I can’t wait to dive in head first and push the boundaries of what’s possible.

To my friends at Sprout Social whom I’ve worked with over the past 11 years: Thank you for being such a joy to work with each day, and so focused on building human centered work first and foremost.

To my new friends at RWX, I can’t wait to ship some amazing software together!

For anyone looking for a faster and more reliable alternative to GitHub actions, please reach out if you want to talk RWX.

Onward!


»

You Should Host Your Own Code Forge

Back in April, GitHub shared a staggering graph of their scaling challenges:

GitHub Repository and Commit Expansion

LLMs are producing code at an almost frightening rate, and if you use GitHub on a semi-frequent basis, you’ll know that it’s down quite regularly these days as a result of the onslaught.

For my own personal work, rather than tolerate the GitHub instability, I’ve instead opted to self-host my own Forgejo instance in my basement server rack.

Smith Cottage Internal Forgejo instance

This is yet another important step in reclaiming my own computing sovereignty. While the world is busy spraying gigatons of slop all over GitHub, I’m taking back ownership of the code that’s always been mine. Growing in my craft means not just owning the work, but also building the tools and the environment that the work gets produced in. I aspire to build the Hans Zimmer music studio of computing.

Hans Zimmer Music Studio

Running my own private code forge has been a joy, especially with “push to create repository” Forgejo feature turned on. This enables any whimsical hairbrained idea to quickly become a git repository stashed for my own private creation. If I want to live a creative life, full of Big Magic, I have to start with the basics: doing a huge volume of work. A private code forge is a great scratch-pad to sink ideas into.

If you’re looking for a sign to bring your code “back home”, either personally, or at your company, the graph above might be the right signal that it’s time to take a look at self-hosted options. Forgejo is definitely worth a look!


»

The Server Rack Expands

The server rack continues to expand! In an effort to buy hardware before the AI bubble continues to drive up computer hardware prices, I’ve added three more Minisforum UM690L mini PCs to the basement rack (this time in black!).

Expanded Server Rack

I’ll be using this new batch of machines to separate a testing cluster from “production” infrastructure that runs the stuff in the house (Home Assistant, Jellyfin, etc.)

I haven’t yet isolated the network switching / routing, but that’ll come at some point.

In the meantime, I’ll keep on cheering for the AI bubble to crash in hopes of computer hardware returning back to earth.


» all posts