Slinging bytes through servers @laravel
Connecticut, USA
Joined September 2010
- Tweets47.9K
- Following503
- Followers19.3K
- Likes47.7K
what if this is describing one person?
challenge accepted
Every office at 4:30 on a Friday:
- The Ghost: green dot on Teams but has been at happy hour since 2
- The Hero: sends a "quick question" email that ruins three people's weekends
- The Martyr: "I'll just hop on for a bit this weekend," said loud enough for the manager to hear
- The Blocker: has had "Focus time" on the calendar from 3 to 5 every Friday for two years
- The New Guy: still at his desk. Nobody told him.
- The Manager: "Let's circle back Monday." Will not circle back Monday.
Things not to slop (or to have a lot of guard rails around)
- code that manages infrastructure
- stuff that sends email
Chris Fidao retweeted
A fun QoL improvement we shipped to Cloud recently: now when you enable a feature that requires a package your app doesn't have installed, we warn you before you deploy. As soon as we detect that you've installed the package, the warning goes away and you can ship 🚢
Chris Fidao retweeted
Still haven't read or written a single line of code. But I did need to understand why Claude built my checkout architecture in a way that felt really clunky.
So I investigated 👇
Chris Fidao retweeted
Laravel is hiring a designer to join the Laravel Cloud team!
If you're a designer that loves to sweat the details and make complex flows feel simple, DM me.
Chris Fidao retweeted
What's running alongside Laravel in your stack? We want to know!
Tell us about the other languages and frameworks powering your projects in our three-minute survey.
Take the survey → forms.gle/TdqmHnbT6qEDN6XB9
Chris Fidao retweeted
I’ll send a new MacBook Air (good config nothing lame) to the best side project shipped on Laravel Cloud this weekend
Not a drill please be somewhere I can actually ship it to
Reply to this tweet with a laravel.cloud URL
Chris Fidao retweeted
This is the main way I build anything big now.
First, I have a nice long conversation with an agent and arrive at a plan I feel good about. That agent writes the plan to a Solo scratchpad (durable markdown doc, via MCP)
Then I have that lead agent spawn new agents to review the scratchpad looking for gaps. They all write back to that same shared doc, via MCP. (That's what's happening in the images below)
The lead agent sets a wakeup timer so that it doesn't busy-loop or bother the subagents. Solo will wake it up.
When all the agents are done, the lead agent gets woken up to synthesize. Then we chat some more about what they found.
After I feel super confident in the plan, the lead agent takes over in an "orchestration" role. I don't need worktrees, and I don't care how many agents get spawned. That's up to the lead agent to make sure everyone stays in their own lanes. The agents are smart enough to do this!
Using Solo's MCP, it just interacts with the terminals and tells all the subagents what to do, based on our plan. It's reading and writing directly from/to the terminal panes.
When we're all done, I run a round of reviews comparing what was built versus the planning doc to see if we covered it all.
Chris Fidao retweeted
We've just shipped some solid improvements to web worker / FPM metrics on Laravel Cloud. 📈
When viewing web worker metrics, you can now see a breakdown of active, idle, and "limit", where limit is the maximum amount of web workers that can be created across every replica of your application.
Chris Fidao retweeted
Started a new YouTube channel as an outlet for my obsession with home gym equipment 😄 Just published the first video!
Chris Fidao retweeted
This week on MT @aarondfrancis's got a new theory he's trying out on @IanLandsman:
In the AI era, languages don't matter as much - but frameworks & ecosystems, especially batteries-included frameworks like @laravelphp, increasingly do 🔥