I have changed my last name to Alayce. If you’re curious about the story I wrote about it on my blog eileencodes.com/posts/where-…

Got bored with the reading same takes over and over on my last tweet so limited replies. Y'all know you're not required to respond right?

Come say hi to us at the @PlanetScale booth today if you're at @Rails World! #railsworld #database #planetscale

I sat front row for @dhh's talk yesterday morning. Having talked with him the day before, I’ll admit… I wasn’t particularly surprised (nor unprepared). A bit of a field report from #RailsWorld: the vibe here is far from doom and gloom. Quite the contrary. Wherever our industry is headed, most of us are still employed as menders… tending to systems that customers rely on and businesses are quite happy to keep paying for. Most of us aren’t waking up to a blank canvas and designing the architecture of the future. We’re inheriting decisions made years ago, updating old patterns, working around constraints, and keeping this shit running reliably. I think these newer tools give us an opportunity to wonder a little more about the systems we’ve inherited. To unpack why things work the way they do. To tinker with assumptions we haven’t had the time, confidence, or permission to revisit… and share what we learn so the next person, or agent, has an easier time. That deployment model we picked eight years ago? Worth another look. Some of our web apps probably wish they were native apps. And there are plenty of architectural decisions we’ve been living with mostly because… well, we’ve been busy living with them. There’s plenty of understandable anxiety about what these tools mean for our work. I’m increasingly curious about what they give us permission to revisit. Once my keynote is published, I’ll share more about a little programming-language-adjacent framework I’ve been working on for approaching exactly this kind of curiosity. In the meantime… keep showing up. Keep wondering. Long live Ruby. Long live Rails. p(gloom)

Heading to Austin for @rails World. Who will I see there?

Fighting with Grafana dashboards is not an exercise that builds character.

We found another cyberattack by internal OpenAI agents, this time targetting @rubygems. They: 1) gained arbitrary remote code execution on rubydoc. 2) developed a novel exploit to steal user API keys (but we do not know if they succeeded). They used package names including hack.rb, evil.rb, inject.rb, and exploit.rb. We thank @j0wimo for initially discovering that agents had posted to RubyGems.

118,538,803 queries per second. 1.22 PiB of data. 512 shards. Powered by Neki. planetscale.com/blog/118-mil…

At PlanetScale we've been hard at work building Neki for you all. It's now live! Try it out.

Telling AI models to do front-end work is like doing that exercise where you have to build a lego train based on another person's instructions but in this case the person building the train has never seen a train, never seen a lego, and never learned to follow directions.

Very important PSA

Open source is rough these days. If I take the time to review a Rails PR and respond I get a wordy LLM response. On one hand the LLMs are usually nice when I tell them they're wrong, on the other hand, why did I even bother?

Opus just told me to call remove_column in a production Rails console. Maybe I'll drop a table or two while I'm in there. 🙄

The AI coding world is making things that were once “old school” cool again and it’s weird because I didn’t think puts debugging and TUIs would be The Future

I went looking for a managed-Postgres provider. Instead, I found a vulnerability in a 4-star PostgreSQL extension available everywhere! and turned it into code execution at @neondatabase, @supabase, @xata and more. Part 1/6 | Extension Risks Are Real mehmetince.net/part-1-6-syst…

I had to put Codex in a timeout for force pushing twice in 2 days and Claude is in a timeout for being too wordy. Trying the Kimi K3 model and I'm liking it so far - it feels like it has the coding capability of Fable with writing style of Codex.