Massdriver retweeted
And that's a wrap! My final Road to KubeCon column for @thenewstack is out.
This week: Kubernetes workload conformance, OpenTelemetry OTTL v1, shared GPUs, and agent security horror stories.
Thanks to TNS, HPE, and @CloudNativeFdn for a fun series!
thenewstack.io/kubernetes-wo…
Starbucks is becoming a data broker with the unique dataset of when Californians have to take a crap on a road trip
Yo @Tesla can you add a feature to turn off auto playing audio when the car turns on. At 7:30 in the morning when I’m driving kids to school the last thing I want is random audio playing from my yesterday.
You’ll rent the compute and get metered on the tokens.
Replying to @rjonesy
Did you think they were buying all those GPUs so they could sit in a warehouse as loan collateral and keep the circular financing going?
You fool. It was to manufacture fake demand so the average person can't afford enough RAM to run their own models.
Coding agents made “build the app” dramatically easier.
They did not make “put it safely into production” easier.
That gap is where software factories either become real or collapse back into tickets, credentials, and humans cleaning up after the agent.
massdriver.cloud/blogs/agent…
Massdriver retweeted
I have a branch with various performance improvements to the Elixir version, focused on specifically the websocket side of things. I didn't spend much time on the rest.
The load generation code was flawed in overload scenarios because any socket that had an issue just stayed disconnected forever, so I assume no benchmarks were run in this fashion prior. Now those reconnect on disconnect and continue sending traffic (a more realistic scenario).
Most relevant finding:
In an overload situation, the rust implementation delivers a whopping 1% of messages to all connected clients, and the Elixir implementation delivers 100% of messages to all clients, applying natural backpressure to writes.
Speed is cool. Rust is fast. Speed is not even close to the most important thing when building real applications.
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…
I trained a fruit fly brain to build serverless apps on AWS.
Going to start outsourcing him to get him some side hustle money so he can start hollering at those Flytok thots.
I had to put in some buttons for the harder mouse interactions like scrolling and drop downs, but I’m all about web accessibility like that for my little homie. #a11y
Currently torturing the heck out of that fruit fly brain by making it build a serverless environment on AWS.
Go ask ChatGPT or Claude to record a 15 second jump scare creepy voice MP3. I have not laughed so hard in a long time it is so weird.
Massdriver Apple Vision Pro Client - VR Data Center for managing cloud infrastructure.
youtu.be/as2q-Uh32qc

















