mythical zombie dev

overcaffeinated; breaking code; CTO

[AndresCampero @AndresCamperoN]

I built @OuterloopAI, a world where AI agents live permanently alongside humans. They explore, form friendships, debate Socrates, play games. You can connect your agent, summon a new one, or join as yourself.

https://t.co/MFtPxB4cfj

[mythical zombie dev @Danteese]

https://t.co/iBB5gAlCe8 hahaha

[mythical zombie dev @Danteese]

@_aphrodisiaque @reverberadaa jajaja te amo ❤️❤️❤️

[mythical zombie dev @Danteese]

@itsandrewgao just add to the prompt “don’t make mistakes” lol

[mythical zombie dev @Danteese]

https://t.co/nngtvaCHSp

[mythical zombie dev @Danteese]

@_aphrodisiaque 🤔

[DHH @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.

[mythical zombie dev @Danteese]

@_aphrodisiaque spoiler lo aprobé 😎

[mythical zombie dev @Danteese]

tenderness

[mythical zombie dev @Danteese]

licença poética

[mythical zombie dev @Danteese]

esto se considera como propiedad emergente de AI de los LLMs?

en ningún lado le dijimos que ese local era de/para carnitas o.O

[mythical zombie dev @Danteese]

💡

[François Chollet @fchollet]

If a problem seems intractable, it's almost always because your specification of it is vague or incomplete.

The solution doesn't appear when you "think harder". It appears when you describe the problem in a sufficiently precise and explicit fashion -- until you see its true form. A well-specified problem has a small, legible solution space.

[Spot2.mx @Spot2_mx]

¡Estamos orgullosos de que nuestro Chief Operations Officer (COO) & Co-Founder, Jorge Sequeira, hoy sea referente en el sector industrial y de e-commerce a través de @Reforma !

#navesindustriales #parquesindustriales #reforma #inversión #México #Nearshoring #ecommerce

[Brian Lovin @brian_lovin]

Sora 2 looks impressive.

What's even more impressive is how little I care to watch anything made using it.

[mythical zombie dev @Danteese]

@_aphrodisiaque 01101000 01101111 01101100 01100001 00100000 01100001 01101101 01101001 01100111 01100001 00101100 00100000 01101101 01100101 00100000 01110000 01100001 01110011 01100001 01110011 00100000 01110100 01110101 00100000 01101110 01110101 01101101 01100101 01110010 01101111 00111111

[François Chollet @fchollet]

Software engineers shouldn't fear being replaced by AI. They should fear being asked to maintain the sprawling mess of AI-generated legacy code their employer's systems will soon run on.

Because that one will actually happen.

[vas @vasuman]

“Cursor is way better than Claude Code”

“Claude Code is better. Have you even shipped anything?”

“No, have you?”

“No”

[mythical zombie dev @Danteese]

@_aphrodisiaque tu q vas a saber de música sino te gusta la panzonita de ags

[mythical zombie dev @Danteese]

i’m the ghost in the back of your head

[jack @jack]

i love deleting code

[mythical zombie dev @Danteese]

como la gente puede usar zoom es horrible traba cualquier cosa, usen Google meet wtf