Pinned Tweet
Open source has reshaped how we build and maintain software, is reshaping how we build currency and transact with it, and is destined to change how we, as human beings, communicate.
ᴊᴇᴡᴊᴏɴɴʏ.ᴇᴛʜ retweeted
A highly relevant research by @WeizmanGal on the security of "AI Browsers" and their extended attack surface.
Specifically, he discovered a rogue extension could control Google's AI Gemini's side panel in Chrome browser and abuse its privileges.
Replying to @WeizmanGal
I'm on the right side of the curve regarding #moltbook, its the singularity point of the third phase of the internet and I’m so excited
I will debate you live in a podcast that microservices are the best thing invented in software architecture in the last 10 years @dhh
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.
The craziest part is that methods like The Strangler Fig Pattern, DDD, Team Topologies should be the bread and butter of these so called architects but have no business orientation smh
Will debate anyone that micro services for the most part the only way to run a venture capital startup doesn’t matter the size
ᴊᴇᴡᴊᴏɴɴʏ.ᴇᴛʜ retweeted
your kidney can go for like $300k and you only need one to survive
god gave us all startup capital. you just have to want it bad enough
poor managers copy pasting tactics never pay the price for their costly mistakes, its a chronicle disease
At a past company, the head of engineering and the principal engineers decided to break our Ruby on Rails application into a Go microservices mesh.
They created very detailed design documents and architecture diagrams. They went all out and used Kubernetes, gRPC, service templates, the whole shebang.
The whole senior engineering leadership came from Amazon, where they were used to each team owning a distinct service. They tried to apply that model directly. But our issues were with code ownership and poor domain modeling.
The entire application could have run on just a handful of EC2 instances.
What was the result?
Five years later, 70% of the application is still running on the Ruby on Rails monolith. Never completed the migration. But now they have to maintain two systems.
None of the original leadership works there anymore.
















