🚂 to ⌨️ I used to drive trains, now I tell clankers what to do

Joined February 2019
383 Photos and videos
Pinned Tweet
30 Dec 2025
tfw your jobs never fail and your database provider tells you that you don't need your failed_jobs table anymore
2
29
9,764
Claude Fable 5 Build loops that make them cry wolf
Introducing Claude Fable 5: a Mythos-class model that we’ve made safe for general use. Its capabilities exceed those of any model we’ve ever made generally available.
1
73
Sadly not merged but the bug is fixed in the latest version of Pest 🎉
28
I thought the early bird gets the worm but it’s 8:45pm and look what we have here….
1
34
Sending @laravelphp NightWatch webhooks to @cognition to automatically resolve issues 🔥 I included in the prompt to look for existing PRs or commits that aren’t released yet to prevent duplicate fixes. Every bug email already has a first pass fix applied before I investigate
1
5
178
I guess I’ll forgive them for stealing my name
26
valid
1
33
Laravel Cloud automatically deploys but I like running tests before starting deployment, so I often use their deploy hooks, but there's no way to tell it succeeded. This Github Action calls the deploy hook and then waits on the deployment to complete github.com/marketplace/actio…
1
4
100
👨‍🍳
Last week the team shipped Managed Queues on Laravel Cloud - one of our most requested features, and, since I love queues, a project I was deeply invested in. When we started, Laravel Vapor's queues were our north star: we wanted that "it just works" feeling, but without the limitations of running on Lambda. And we wanted to go further. We paired that hands-off Vapor experience with the kind of deep insights and observability you'd reach for Laravel Horizon to get - all built natively into Laravel Cloud. You get queues that just work and you actually get to see what they're doing. I'm really happy with where we landed, and this is just the beginning. laravel.com/blog/managed-que…
37
We’re building an in-house Slack agent and definitely agree. I know Devin AI was iffy in the beginning but I have a lot of respect for their team seeing the experience they’ve built. They’ve done a lot to make it feel natural
this Slack agent is certainly the most difficult engineering project I have touched in a long, long time on the surface its somewhat straight forward, but the amount of moving parts and complexity combined with the fact that much of its not determnistic makes it very difficult
1
96
There’s a lot of edge cases and response times can be difficult especially when you want full codebase knowledge across N number of repos across the org, etc
9
simultaneously showing up as the highest token usage and the least amount of merged work is wild to me
21
Devin Riegle retweeted
Bragging about how much software you’re shipping with AI is like holding down the shutter button and bragging about how many photos you took.
234
675
6,134
243,121
This shows some of the hairiest pieces about the Rust rewrite. They went from building up context on the code for years but now nobody knows it. It’s like everyone on the team is starting from day 1. Nobody feels comfortable to review the code.
Well, I definitely learned my lesson about squandering my time, effort, and tokens on another project that I don't control and have no stake in. Never again.
1
91
It’s going to take time for them to understand it and then more time to be able to easily accept external contributions 1M lines of code built over years of iteration vs 1M lines you’ve never seen is wildly different.
1
36
Also basically every bug report before the Rust version is just going to be told to upgrade. Much easier to apply fixes on Rust than try to write them in two different codebases. Plus the Rust version may have fixed the bug? Who knows
18
Everybody’s scared of RTO but nobody’s talking about return to suits
2
138
This is all subjective but Wispr Flow felt better during the trial than after paying for a subscription. I use it less now because it just completely misunderstands me so often
2
1
91
GitLab: you cannot merge this, you need to refresh the page.
56
Nine…the number of times I’ve had to re-login to GitLab in the last 30 hours Such a pain to use
1
1
481