We benchmarked 10 LLMs on writing infrastructure code: 90 OpenTofu modules for AWS, GCP and Azure.
28% failed a mandatory security item. 0 of 30 S3 modules produced working access logs. Top four within 3 points at a 9x cost spread.
Rankings and code: bit.ly/llm-iac-benchmarks
69
Building Agentic Software Factories on AWS for Citizen Developers teapawt.org/i/broadcasts/2kEvdmNVz…
88
Last night, I became aware of the concerns raised in Josh's post. I reached out publicly and over DM to offer a potential explanation based on the limited information available at the time, while working to understand what happened.
As background, we’ve internally been pushing 100% on security of the Railway platform. At Railway, we believe that cyber threats are real and mounting, and we’ve built out tooling for automatic scanning + CVE remediation (for both our infrastructure and customers). Over the last few weeks, oncall engineers were instructed to red team our infrastructure. We maintain specific policies and short lived grants for when these actions occur.
Subsequently, I became aware that an employee at Railway had constructed, on their own time, a tool for proactive identification + reporting of bug bounties within the broader community.
The employee, using their own personal accounts, personal credit card, and time outside of work hours, signed up for a personal subscription to a hosted service running Deepseek. I can confirm they ran this tool once and only once, on a singular external provider, and halted it proactively within 15 minutes of starting.
Railway does not condone these actions. We expect all our employees to uphold our standards of conduct, whether acting on behalf of Railway or in a personal capacity. We create an environment where internal red teaming has strict guidelines, and when bug bounty disclosures must occur, we follow every letter of responsible disclosure.
We have addressed this incident with the employee directly and have taken appropriate action. We are also reinforcing our expectations for employee conduct to help prevent similar situations.
Readers added context they thought people might want to know
Primcloud does not have a bug bounty program, per its founder. Its Acceptable Use Policy forbids unauthorized probing, scanning or vulnerability testing without prior written consent.
x.com/joshmanders/st…
primcloud.com/aup
1
151
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…
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…
111
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
1
109
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.
54
Massdriver Apple Vision Pro Client - VR Data Center for managing cloud infrastructure.
youtu.be/as2q-Uh32qc
82


















