Ralph Schindler

God, grant me the clarity to accept the problems AI confidently solves, the patience to fix the ones it confidently breaks, and the wisdom to know when I should have written it myself. #FirstDayBackIn2026 #SoftwareEngineering

If you're using rdkafka for php, I would appreciate you giving the 7.x alpha a try. 
The issue backlog has been pared down (35 to 2), and all outstanding PRs have been merged (except 1 big one)... 
Available via pecl or pie. github.com/php-rdkafka/ph…

@joshcirre @taylorotwell more like...

php without laravel

@LeahTCodes I felt this way too... But now that the company has switched from Slack go gChat, I find myself Teams curious 😅

I'm jealous of anyone who goes their whole life without having to use Microsoft Teams

@heystevebauman Yo- I am more than happy to test this out when ready, your approach is ideal. I too needed this, and landed on a package that pulled out the process management into a separate package (that horizon has), and queue monitoring into this: github.com/smwks/laravel-…

Currently battle testing. Hope to have the PR ready soon Let's see what happens! 🫡

@aarondfrancis I wanted all the goodness of Horizon for db workers (metrics/introspection/control) so made this: github.com/smwks/laravel-… ... would love if some of horizon internals made it back to the framework as abstractions. 😀

Database as a queue is an anti-pattern! ...that I absolutely love and do all the time anyway. Definitely worth a read.

@ShaneDRosenthal @nativephp @official_php @reactnative vs. NativePHP which embeds the php interpreter into the swift binary, and it handles the request/response loop in the app binary.. is that an accurate simplification?

@ShaneDRosenthal @nativephp @official_php @reactnative the word embedded is probably a little overloaded in this space. let me see if I am tracking with RN, apps are packaged with native (swift app) binary plus another binary that executes the JS interpreter (embedded meaning packaged)... they talk over a socket/bridge vs. cont..

We’re not even close to done with @nativephp. Can’t wait to prove to the world why inherently @official_php is a better language than @reactnative for mobile development. Any doubters simply don’t understand why at its core it was actually built for this type of work over something like JS. Or they’re just ignorant.

@ShaneDRosenthal @nativephp @official_php @reactnative if PHP has a particular strategic advantage, that's even better news

@ShaneDRosenthal @nativephp @official_php @reactnative we're invested into RN for our next iteration of our app (previously native), that decision is made and moving forward.. but, I'd love to see some high-level tech report/comparison of why NativePHP over RN to understand how they stack up when the next choice needs to be made

@danjharrin @alvinaputri @filamentphp I think she means that on /docs there is no table of contents, that threw me for a loop too for a second, then figured I had to jump into any of the quick links to then find what I wanted.

@alvinaputri @filamentphp 😶 The tricks from the previous website are still published in the Insights section. We have not removed them. We have not had a dedicated Tricks section on our website for nearly 3 years. The documentation also has a complete sidebar, not sure what you are referring to…

Dear @filamentphp team, WTH with new site! The /tricks page gone. The documentation page is horrible with quick links. Just give me the damn complete sidebar.

@joshcirre I think we're trying to solve similar problems: github.com/smwks/tallium

Still haven’t fleshed these thoughts out. But I think it’s extremely important, now more than ever, for you to have an opinionated coding “fence” for your agents. Starter kits are great. But you need a replicable way to build every piece of the tools you create. Opinionated, full-stack, batteries included frameworks like Laravel are fantastic. But I still think they are just a starting point. A fantastic one. But a starting point nonetheless. They help tell agents how to write the code and how to build a fence. But if you already have opinions on what that fence looks like, then the speed you can build things becomes insurmountable. What components look like, how styling works, what patterns in back end code you want, what API patterns might look like, how DX/UX should feel. Frameworks, even batteries-included ones, still have flexibility and freedom. Humans (you) driving that freedom feels so much better than having agents pick those choices.

8.5 years into this espresso machine, and we've had 2 close calls. 1st was remedied by replacing the grinder. Then had to do deep surgery to clear out a blocked tube from heater to milk/water steamer... Successful surgery and now onward to espresso 10,000 #delonghi #espresso

@joshcirre for context, I was trying to not use jobs/reverb, but achieve a nice ux where message send appears -> "thinking" bubble, livewire component waits on agent responses and streams them to the frontend. I've moved back to ->prompt() temporarily, but would love insight :D THANKS!

@ralphschindler I don't have any example code just yet, but that's a great opportunity for me to put a demo together. Give me the day today. 👀

Guess what? This is all still Livewire Flux. 😮‍💨

New in 2026: AI orchestration apps are the new TODO apps. Seems like everyone is writing one. All very different- not many similar approaches, massively different perspectives.. Everyone wants to get to gas town in their own vehicle on their own highway.

@jeffrey_way Pulling data from a WiFi/BT scale?

It's been said a thousand times, but this really is the year of personal software. Can't find an app that fits your needs? Take five minutes to write a plan, and then create a bunch of tasks for enhancements you require. Go have a dinner, and it'll be done when you're finished.

@joedevon I’ll guess 2% loc I wrote, that said, deep deep spec writing. I didn’t one shot this. 16 phases to plan

@ralphschindler How many loc did you write yourself vs AI?

For the first time in my life, I built a complete enough project ready to ship and I have yet to buy, or even think about a good domain name for it. Wild time to be a developer.

looking back, the choice to go with a conventional framework seems to be paying dividends in this new agentic coding age

Something I've been saying for almost as long as I've been using Laravel (~10 years): Prescriptions > Patterns Patterns alone will guide to you infinitely different (arguably still "right") solutions. Prescriptions lead to finitely variable / idiomatic solutions.