woo

I'm building Tribely - a Kanban-Style tool that gets back to the roots of speed and simplicity, inspired by Pivotal Tracker. Friends advised me to start gathering an interest list. So, here's the invite: tribely.work My promise to you: ❌ No newsletter. ❌ No marketing spam. ✅Only one email right when we launch. Thank you for support. #buildinpublic #RubyOnRails #Hotwire #SaaS

Took a short break from shipping features for Tribely, but I'm back. Just wired up the Discord integration. You can try to use discord/slack/webhooks to work with your army of #AI agents and manage tasks in Kanban-Style. The Rails 8.1 monolith just makes sense for solo building. #buildinpublic #RubyOnRails #Hotwire

Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table. Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication. Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.” Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it. The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks. Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.

@dhh @jorgemanru @excid3 take a look if you have time

I've temporarily opened registration for Tribely.work! 🔓 For the next 2 hours, you can create an account and enjoy unrestricted access to every feature. The window closes today around 2 PM UTC, so grab your spot while you can! #rubyonrails #buildinpublic #hotwire

Fizzy is Open Source just like North Korea is Democratic. Read more here: ma.tt/2025/12/dhh-op…

@bradgessler Didn't know about Superform. Will definitely try it in next project with Phlex. I used SimpleForm out of habit... I know it best.

@woochaq Yeah I tried them all: simple_form, formtastic, Rails form helpers and determined they all suck, especially with Phlex.

At Tribely it looks like this... Mostly because of using Phlex #rubyonrails #buildinpublic #hotwire

@bradgessler Ah, I see you are contributor ofr Superform :)

@woochaq Same. Are you using Superform?

@bradgessler No. I use `simple_form` github.com/heartcombo/sim…

Blog post nextjs.org/blog/CVE-2025-…

This is unbelievable. You pay Vercel’s premium prices so things are supposed to be easier for you. And then #Vercel blocks the deployment of your own app because you must upgrade to the latest #Nextjs version (which may be incompatible with your libraries). On Vercel, your code is no longer your code! #rubyonrails #nextjs #react

Works perfect ! I've been waiting for nest list items :) #rubyonrails

Here we go again: Only API and Dashboards: cloudflarestatus.com #cloudflaredown

@dayyanl Should be easy

@woochaq Simple fix, right?

It's cool that people are reporting bugs, but some are taking it way too seriously :). It's not hard to do optimistic updates with Rails and Hotwire. If I managed to do it, the #FIZZY guys will sort it out in no time. #hotwire #rubyonrails

@ccssmnn @a13r___ Not everything needs auth, and Devise is a breeze to use anyway.

@woochaq @a13r___ yeah when i was looking into rails a few years ago i was shocked it doesn't come with auth built in, and sticked to what i'm already good at.

I dug a bit into the #FIZZY code and I’m surprised. They use basically a vanilla Rails gem set without any of the libraries considered "standard" these days like Devise, ViewComponent, Phlex, RSpec, etc... Nothing fancy, zero bloat. I thought I was a purist at Tribely, but @37signals takes it to a whole new level. I bet that was @dhh's intention all along. Mad respect for this approach. Great job and amazing study material 👍

@dhh @dhh be honest, you're trolling them on purpose just for marketing, right? :)

Love how calling Fizzy open source is triggering some because our MIT-derived O'Saasy License reserves SaaS monetization rights to us as creators. Same nerds will demoan lack of "sustainable OSS" or argue that handing over all changes under GPL is akshually freedom. Hilarious.

@woochaq Only using a single core to run your test suite in 2025 is self-sabbotage 😂. Also, stay away from factories. You need fixtures for this kind of performance.

@dhh Europeans style ...

Whenever I see programmer salary numbers from Europe, I always have to do a double take. It's hard to fathom that we work in the same industry. With bonuses this year, many of our folks are at $400,000+, and we're not even in any AI-hype sector.

The Fizzy test suite runs in UNDER FOUR SECONDS! Nearly 2,500 assertions. The magic is to lean hard on vanilla Rails fixtures and parallel test runners. Not only is this blazingly fast, but it's also achingly beautiful. github.com/basecamp/fizzy…