Made Basecamp and HEY for the underdogs as co-owner and CTO of 37signals. Created Ruby on Rails. Wrote REWORK, It Doesn't Have to Be Crazy at Work, and REMOTE.
Kanban is a simple, practical approach to visually managing processes and backlogs by moving work cards from one progress column to another. Toyota came up with it to track their production lines back in the middle of the 20th century, but it's since been applied to all sorts of industries with great effect. And Fizzy is our new fun, modern take on it in digital form.
We're certainly not the first to take a swing at this, not even for software development. Since the early 2000s, there's been a movement to use the Kanban concept to track bugs, issues, and ideas in our industry. And countless attempts to digitize the concept over the years.
But as with so much other software, good ideas can grow cumbersome and unwieldy surprisingly quickly. Fizzy is a fresh reset of an old idea.
We need more of that.
Very little software is ever the final word on solving interesting problems. Even products that start out with great promise and simplicity tend to accumulate cruft and complexity over time. A healthy ecosystem needs a recurring cycle of renewal.
We've taken this mission to heart not just with Fizzy's fun, colorful, and modern implementation of the Kanban concept, but also in its distribution.
Fizzy is available as a service we run where you get 1,000 cards for free, and then it's $20/month for unlimited usage. But we're also giving you access to the entire code base, and invite enterprising individuals and companies to run their own instance totally free of charge.
This is done under the O'Saasy License, which is basically the do-whatever-you-want-just-don't-sue MIT License, but with a carve-out that reserves the commercialization rights to run Fizzy as SaaS for us as the creators. That means it's not technically Open Source™, but the source sure is open, and you can find it on our public GitHub repository.
That open source is what we run too. So new features or bugs fixes accepted on GitHub will make it into both our Fizzy SaaS offering and what anyone can run on their own hardware. We've already had a handful of contributions go live like this!
Ultimately, it's our plan to let data flow freely between the SaaS and the local installations. You'll be able to start an account on your own instance, and then, if you'd rather we just run it for you, take that data with you into the managed setup. Or the other way around!
In an age where SaaS companies come and go, pivot one way or the other, I think it's a great reassurance that the source code is freely available, and that any work put into a SaaS account is portable to your own installation later.
I'm also just a huge fan of being able to View Source. Traditionally, that's been reserved to the front end (and even that has been disappearing due to the scourge of minimization, transpiling, and bundling), but I'm usually even more interested in seeing how things are built on the backend. Fizzy allows you full introspection into that. Including the entire history of how the product was built, pull request by pull request. It's a great way to learn how modern Rails applications are put together!
So please give Fizzy a spin. Whether you're working on software, with a need to track those bugs and feature requests, or you're in an entirely different business and need a place for your particular issues and ideas. Fizzy is a fresh, fun way to manage it all, Kanban style. Enjoy!
Black Friday is usually when ecommerce sets new records. This has certainly been true for Shopify through most of its existence. So much so that the company spends months in advance preparing for The Big Day(s). You'd think after more than twenty years, though, that things would have leveled out. But you'd be wrong.
This year, merchants sold an astounding $6.2 billion worth of wares through Shopify on Black Friday. That's up 25% from last year, when the record was ~$5 billion. Just crazy high growth on a crazy big base. The law of big numbers clearly hasn't found a way to apply itself here yet!
That volume of orders means the Shopify monolith gets put through its paces. The backend API peaked at 31 million requests per minute. The databases carried 53 million reads and 2 million writes per second. Bonkers.
Rarely do the stars align to shine so brightly that a single company is stewarded by a still-active programmer with a stellar pedigree of core contributions, saddled with such unceasing success, faced with a constant barrage of novel technical challenges, and willing to contribute everything they learn and build back into the open-source base pillars. But that's Shopify.
Ultimately, this is all downstream from being a founder-led business. Tobi Lütke not only served on the Rails core team in the early days, but continues to steer the Shopify ship with a programmer's eye for detail and exploration. The latest release of Omarchy even features his new Try tool. How many CEOs of companies worth two hundred billion dollars still program like that?
Despite all this, there's occasionally still some fringe consternation in the Ruby world about Shopify's dominance. In Rails, Shopify employs almost half the core contributors. In Ruby, they have several people on the core team too. Seeing this as anything but a blessing is silly, though.
We wouldn't have such battle-tested releases of Rails without Shopify running production on the framework's edge. We wouldn't have gotten YJIT without the years of effort they sunk into improving Ruby's core performance. And we wouldn't have seen the recent production-proving of Ractors without them either. Any programming community should be so lucky as to have a Shopify!
Now I'm obviously biased here. Not only have I been friends with Tobi for over twenty years, but I also serve on the board of directors for the company. I'm both socially and economically incentivized to cheer for this extraordinary company. But that doesn't mean it isn't all true too!
Shopify is indeed the patron saint of Ruby on Rails. Its infrastructure team is the backbone of our ecosystem, and its continued success the best case study of how far you can take this framework and language. They deserve a gawd damn parade for all they do.
So on this Cyber Monday, I say cheers to Tobi, cheers to the thousands of Shopifolk. You're killing it for merchants, shoppers, and all of us working with Ruby on Rails. Bravo.
It's pretty incredible that we're able to run all these awesome AI models on our own hardware now. From downscaled versions of DeepSeek to gpt-oss-20b, there are many options for many types of computers. But let's get real here: they're all vastly behind the frontier models available for rent, and thus for most developers a curiosity at best.
This doesn't take anything away from the technical accomplishment. It doesn't take anything away from the fact that small models are improving, and that maybe one day they'll indeed be good enough for developers to rely on them in their daily work.
But that day is not today.
Thus, I find it spurious to hear developers evaluate their next computer on the prospect of how well it's capable of running local models. Because they all suck! Whether one sucks a little less than the other doesn't really matter. And as soon as you discover this, you'll be back to using the rented models for the vast majority of the work you're doing.
This is actually great news! It means you really don't need a 128GB VRAM computer on your desk. Which should come as a relief now that RAM prices are skyrocketing, exactly because of AI's insatiable demand for more resources. Most developers these days can get by with very little, especially if they're running Linux.
So as an experiment, I've parked my lovely $2,000 Framework Desktop for a while. It's an incredible machine, but in the day-to-day, I've actually found I barely notice the difference compared to a $500 mini PC from Beelink (or Minisforum).
I bet you likely need way less than you think too.
I haven't done a full-system backup since back in the olden days before Dropbox and Git. Every machine I now own is treated as a stateless, disposable unit that can be stolen, lost, or corrupted without consequences. The combination of full-disk encryption and distributed copies of all important data means there's just no stress if anything bad happens to the computer.
But don't mistake this for just a "everything is in the cloud" argument. Yes, I use Dropbox and GitHub to hold all the data that I care about, but the beauty of these systems is that they work with local copies of that data, so with a couple of computers here and there, I always have a recent version of everything, in case either syncing service should go offline (or away!).
The trick to making this regime work is to stick with it. This is especially true for Dropbox. It's where everything of importance needs to go: documents, images, whatever. And it's instantly distributed on all the machines I run. Everything outside of Dropbox is essentially treated as a temporary directory that's fully disposable.
It's from this principle that I built Omarchy too. Given that I already had a way to restore all data and code onto a new machine in no time at all, it seemed so unreasonable that the configuration needed for a fully functional system still took hours on end. Now it's all encoded in an ISO setup that installs in two minutes on a fast computer.
Now it's true that this method relies on both multiple computers and a fast internet connection. If you're stuck on a rock in the middle of nowhere, and you somehow haven't discovered the glory of Starlink, maybe just stick to your old full-disk backup ways. But if you live in the modern world, there ought to be no reason why a busted computer is a calamity of data loss or a long restore process.
The only way many tech workers in the US can get a long break is by quitting their job. So lots of them do that every few years, which is partly why the average tenure in our industry is at an atrocious 18 months. But this terrible rate of churn is often avoidable by one simple benefit trick: Sabbaticals.
We've been giving everyone at 37signals a six-week sabbatical every three years for the last fifteen years or so. It's been magical for retention because a break like that allows the mind to reset in a way a two-week vacation never could. And when employees yearn for such a reset, the typical option is usually just to quit.
I know the idea of a six-week sabbatical might sound strange to many Europeans who'd be forgiven for thinking "isn't that just August"? And they're not exactly wrong. Europeans usually do enjoy more vacation time, but in the tech industry, that also comes with much lower pay. Easily half to two-thirds less.
I think it's entirely possible to have it both ways: Work for an American tech company with American pay levels, but also enjoy a regular full reset, without having to quit to get it.
And the argument for the boss doesn't even have to be some humanistic plea about long-term happiness. It can simply be about retention: it's very expensive to see smart, trained people walk out the door.
I'd even argue that bosses — be they founders or professional executives — benefit just as much from a regular sabbatical like anyone else. Whenever Jason or I have taken one, we've always come back with fresh ideas and perspectives that invariably lead to positive changes or new ambitions that wouldn't have come otherwise.
Six weeks is also just long enough to remind tired founders that selling their company isn't likely to be the bliss they imagine. That mojito island gets boring quickly. That by week five, they're probably already antsy to get back to the action. There are endless stories of founders who regret selling their business when all they needed was a six-week break from the startup sprint.
Bottom line is that we all need a long break every now and then. Not just two weeks on Mallorca, but time enough to get bored. To get hungry for the intellectual stimulation of work and the social connection of colleagues. The sabbatical is a great way to deliver that and keep founders from wanting to sell and employees from wanting to quit.
As Omarchy was taking off this summer, and thousands of happy users started expressing their delight with the system, I kept waiting for the universe to balance the scales of passion. Nothing of note in this world is allowed to succeed without spawning a counteracting force of haters. And now they're finally here.
The same happened twenty years ago with Ruby on Rails, but back then I still thought you could argue your way to understanding. That if you just made a logical case to counter whatever objections were raised, you'd be able to persuade most haters to change their perspective. How naive.
It was Kathy Sierra who changed my perspective on this. From being annoyed by straw men and non sequiturs to accepting them and the haters as a natural consequence of success. That if you want people to love your creation, you have to accept the opposing force. Yin and yang.
Here's how Kathy presented the choice:
It's safe there in the gray middle. Nobody is mad at you, nobody is making any bad-faith arguments, but also, nobody cares. Lots of work exists in this zone. And that's fine. We don't need every project to reach the moon! But when escape velocity is achieved, you can't avoid drawing energy from both sides.
All this isn't to say that all objections, skepticism, or criticisms come from haters. Far from it. But once sufficient success is secured, a large portion will. It's just that kind of planet, as Jim Rohn would say.
The trick is to see this in aggregate as a necessary milestone. One that's even worth celebrating! Have you even made something worth cheering for, if there isn't a contingent there to boo at it too? Probably not.
So embrace the boos as you embrace the cheers. They come as a pair.
