Pinned Tweet
tfw your jobs never fail and your database provider tells you that you don't need your failed_jobs table anymore
If we're all just directing AI to do things, why is AI incapable of producing reasonable high-quality PRs with helpful diagrams and comments explaining why approaches were taken?
--
It used to require memorizing the inner workings of git, now it's just pure laziness. No excuse
Devin Riegle retweeted
A slide from our last all hands.
I've also started to call out this behavior publicly in Slack channels.
Tired of consuming workslop
I’m glad they’re letting me know in advance.
I figured Y2K was going to take my site down anyways, but @weebly is doing it before that happens
🤞ran into an issue where Pest wouldn't show any output when hitting a segfault inside an agent, hoping this fixes it. Maybe i'll get my first Laravel PR merged
github.com/laravel/pao/pull/…
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
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…
👨🍳
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…
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
simultaneously showing up as the highest token usage and the least amount of merged work is wild to me
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.
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.
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.

















