Pinned Tweet
I was paying >$300/month for accounting software that couldn't send invoices reliably. So I built Zippato.
Carlos Souza retweeted
Next year, I will assign one of my jira tickets to every kid in America.
This will be the first of many.
Latte Macchiato update: used a little bit of honey syrup and the espresso layer settled in the middle a lot easier.
A verdadeira rinha de backend! Ansioso pra acompanhar a contribuição da galera e ver esses números🍿
I've had agents implement and optimize the Campfire web app in Elixir, Go, and Rust. Yes, Ruby is the slowest. I didn't care about that when the pay-off was huge in terms of productivity and developer joy. But if you're no longer reading the code? github.com/basecamp/once-cam…
Readers added context they thought people might want to know
The shown benchmarks use non-equivalent implementations: Elixir routes all DB queries through a single GenServer with Redis for jobs (retained from Rails), while Rust uses in-process queues, omits CSRF tags/fields, and applies other caching changes.
github.com/basecamp/once-…
raw.githubusercontent.com/basecamp/once-…
github.com/basecamp/once-…
github.com/basecamp/once-…
x.com/zachsdaniel1/s…
Carlos Souza retweeted
I mixed Jev + an espresso (state) machine.
Turns out, Jev's a pretty good barista ☕
Introducing Jevspresso: XState determines what's possible, Jev decides the next move. Order in plain language, or break stuff and watch Jev cope.
Try it: jevspresso.dev









