Mike Benner

Never do you see unbridled enthusiasm and shattered dreams mixed so cohesively like you do at McCarran Airport in Las Vegas

Me: “OMG Barkley is on!!” Normal person: “The what?” Me: “It’s this crazy race in TN that only 20 ppl have finished in 40 years.” Normal person: “Wow, are you gonna watch?” Me: “You don’t watch, you follow some guy’s Twitter!” Normal person…. #barkleyconversations #bm100

Here is my take on why Elixir is the best language for AI: immutability, documentation, stability, and tooling for coding agents. It builds on the recent study in which Elixir had the highest completion rate across models among 20 different languages. Link in the thread below.

THE MINIMALIST STACK Ship any product in 2026 👇 No hype. No over-engineering. Just shipping. 1/ Rails — one-person framework, LLM-efficient, fast enough! @rails 2/ PostgreSQL — proven (UbiCloud / Supabase / VPS) 3/ VPS — Hetzner / OVH / whatever works 4/ Kamal — deploy without ceremony 5/ APM — see production as it is (ActiveRabbit.ai) What’s missing? What is your stack?

This has been said a thousand times before, but allow me to add my own voice: the era of humans writing code is over. Disturbing for those of us who identify as SWEs, but no less true. That's not to say SWEs don't have work to do, but writing syntax directly is not it.

Supervision trees are fault tolerant. Now they are self-aware. Introducing Beamlens: Adaptive runtime intelligence for the BEAM. It embeds AI agents directly into your supervision tree to diagnose incidents, analyze state, and self-heal in real-time. Here is how it works 🧵👇

Rails doesn’t scale! …right?! 💎 🚀 One of the biggest performance achievements this year is Shopify! @ShopifyEng Rails monolith proved the opposite: • App servers: 117M requests/min • API: 31.8M requests/min (peak) Rails + Ruby infra + great engineering = internet scale. @rails Also: still one of the best choices for an MVP. (going into 2026)

Biggest web scraping company in the world is suing a web scraping company for web scraping its content obtained through web scraping.

@claytonlz Grok animated

LOL

@claytonlz The stubble

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.

@claytonlz WisprFlow

superwhisper has been increasingly unusable lately and now this... Each time I use it it's like rolling the dice 😆😭

I've walked into Rails shops that use React on the front-end and was stunned at how low-level they have to get to build basic UI interactions. I'm talking about something as simple as form validations. Hotwire works 90% of the time without all the minutiae.

54 years ago today, "The Oregon Trail" computer game was first released.

@dneighbors @KLASSIQTUNEZ That lunch money pouch

@KLASSIQTUNEZ Kangaroos

A shoe brand everybody used to wear that these kids today have never heard of ?

@mitch0z IRONMAIDEN

Tried an AI influencer with nano banana today. Thread 🧵👇

@sciencegirl What if I only see Godzilla?

Apparently if you’re right-brained you see a rabbit, if you’re left-brained you see a turtle. What do you see

The wait is finally over, the Core One INDX by @Prusa3D and @BondtechAB is finally here!! 😍😍 blog.prusa3d.com/introducing-th…

@sciencegirl Not getting divorced

@aastha_mhaske AGENT