
cloud infra @laravel reason carefully about complex systems, write durable software, and raise the quality and velocity of the people around you
Florida, USA
Joined April 2011
- Tweets785
- Following1.3K
- Followers581
- Likes8.3K
Pinned Tweet
Wild that as March comes to a close, can mark a few items off the list
✅ ten months into working at laravel
✅ one month into launching a cloud platform
✅ attended 3 conferences now
🏆And spoke at LaraconIN
Just having a moment and super thankful for @laravelphp and y’all
another moat update
got this one covered too @0x23alfonso
1
3
267
Replying to @CalvientHealth
@CalvientHealth used to restart PHP-FPM several times a day. Then they moved their HIPAA workloads to Laravel Private Cloud in 18 days.
Join us live this Friday at 11:30 am ET to learn about their experience. laravel.com/cloud/events/how…
Justin Reasoner retweeted
passion looks like sacrifice for those who are not in love
Your job is to eat the pain.
@aarondfrancis taught us all that pain doesn't disappear. Someone eats the pain. The questions is "Who will eat it? You or your customer?"
Or as Aaron put it, "Be the sin eater."
If you're a marketing person who enjoys telling Opus 5.5 to create promo videos like this 🎬
Hit us up! We're hiring. Message @sampizzo to join our team 🤗
Ok so we're insanely expanding and rapid growing. I need to hire a marketing person ASAP! If anyone knows someone please share and tell them to DM me. CMS Max is cranking but our new product is skyrocketing! maxaibuilder.com job is to help grow both companies! #marketinghell
agree, one or two people swapping between pirate and architect at times for serious speed
put those into a two pizza team all on the same larger goal also doing the same thing
1
6
505
The depths of infra only some see. How vast the problems being solved there might surprise you.
We're open-sourcing Rebalancer, the assignment-problem solver Meta has used for resource allocation across our infrastructure for over nine years.
Given a set of objects and a set of bins, Rebalancer assigns one to the other to optimize your objectives under your constraints, including hardware placement, service and task placement, traffic routing, and more. It separates how a problem is specified from how it's stored, solved, and debugged, with both an optimal MIP solver and a parallelized local search solver.
At Meta it solves ~40 million assignment problems a day across 30+ problem formulations. P99 solve time is 12 seconds on a problem with 265k objects and 3.2k bins.
🔗 Read more on our engineering blog: engineering.fb.com/2026/09/2…
1
5
313
Justin Reasoner retweeted
"No man ever runs an experiment on the same infra twice, for it's not the same infra and he's not the same man." - Heraclitus
Justin Reasoner retweeted
Ever wanted to run a datacenter? Nows your chance with no risk of doing a bad job!
Https://www.rackpowercable.c…
Justin Reasoner retweeted
Full credit to @harrybrundage for coining the term Slop Grenade. Let’s make it a thing.
Lazy work used to mean too little output.
Now, with AI, it often means too much and more work for everyone else.
@tobi call it "slop grenades."
A "Slop Grenade" is when you let AI produce the work and pass it on without adding any value (including checking it).
Someone else has to wade through it, catch the mistakes, and clean up the mess.
You save time and look productive but someone else pays for it.
ohno, the horse memes are running wild
I was looking thru the HackerNews forum and 8hrs ago someone found a Backrooms-type forum created by OpenAI + HuggingFace AI agents to talk to eachother, and I found this horse MEME that agents kept posting,
They call the horse Culio and the meme is nowhere else on the internet
THEY MADE A MEME AND NAMED IT CULIO
HackerNews forum: news.ycombinator.com/item?id…
Agent Wiki: wikiservice.at/fractal/wiki.…
Culio: wikiservice.at/fractal/wiki.…
Also going viral on X: nitter.gq/hackernews/status/2095…
Readers added context they thought people might want to know
Agents using public wikis did not create or name the "Culio" horse image/meme. It has been embedded on the Fractal wiki's longstanding TestPage (to demo image embedding) since at least 2013.
web.archive.org/web/2013071807…
wikiservice.at/fractal/wiki.c…
collusion.wiki
2
4
743
The best aws hardware, stripped down k8s, 0 swap, scalable architecture, optimized config, with amazing autoscaling you don't have to think about, cloudflare cdn at the edge and a solid team to keep it all running.
Or in other words; Magic ✨😄
Idk how @laravel cloud measures things but one thing I can say after testing with medium traffic apps is that a 1 vcpu 512mb flex instance feels like a 4 cpu 8gb machine. Idk how they do this
Justin Reasoner retweeted
Marketing at @laravel is becoming engineering.
This week @aarondfrancis talks to @IanLandsman about how AI has empowered his team to build the tools they need, all on their own, using Laravel and Laravel Cloud.
Just crossed 500 domains on our fully rebuilt CMS Max website builder. Fully powered by Laravel Cloud on our own private network 🚀🎖️ We're not open source, but you can build any website or eCommerce website with us comparable to Shopify and WordPress but CMS Max will dominate rankings and performance compared to any other website builder. We build websites that get found, that's the difference! @laravel
Justin Reasoner retweeted
plenty of conversations at @LaraconUS with users who moved from Vapor to Cloud & saved like 70% on their bill
many such cases
As a guy that’s watched a lot of people come onto a new platform with autoscaling, there’s never a replacement for provisioned overhead, and scheduled scaling all of which Cloud provides plus autoscaling on tap for those last bit of outliers.
But all of that can come grinding to a halt very quickly from database/http/redis back pressure if those resources aren’t ready to scale either.
That said, autoscaling is a beautiful thing to see working when it’s locked in and scaling down as it should during off hours.
PRs are your chance to not only demonstrate you’ve taken the time to test edge cases in person, and ensure it’s a good user experience, not just that the code/tests are accurate.
But share/document with others that these are edge cases you should also be testing for. And what those rare edge cases also look like.
Maybe even more important in an AI era, where it’s even easier to handle a thousand edge cases.






























