When configuring queues the next value should be higher to avoid cuncurrency: โข๏ธ atomic lock < ๐ backoff (if fails) < โฒ๏ธ timeout < ๐ retry_after (if crashes)
@taylorotwell If you have a job that times out after 5 minutes but a queue that retries after 60s, you end up with jobs that get processed twice. I'm not sure there's any way around it, but I've always wished for one attribute (job timeout) instead of two (time + retry after)
Last quarter I rolled out Microsoft Copilot to 4,000 employees.
$30 per seat per month.
$1.4 million annually.
I called it "digital transformation."
The board loved that phrase.
They approved it in eleven minutes.
No one asked what it would actually do.
Including me.
I told everyone it would "10x productivity."
That's not a real number.
But it sounds like one.
HR asked how we'd measure the 10x.
I said we'd "leverage analytics dashboards."
They stopped asking.
Three months later I checked the usage reports.
47 people had opened it.
12 had used it more than once.
One of them was me.
I used it to summarize an email I could have read in 30 seconds.
It took 45 seconds.
Plus the time it took to fix the hallucinations.
But I called it a "pilot success."
Success means the pilot didn't visibly fail.
The CFO asked about ROI.
I showed him a graph.
The graph went up and to the right.
It measured "AI enablement."
I made that metric up.
He nodded approvingly.
We're "AI-enabled" now.
I don't know what that means.
But it's in our investor deck.
A senior developer asked why we didn't use Claude or ChatGPT.
I said we needed "enterprise-grade security."
He asked what that meant.
I said "compliance."
He asked which compliance.
I said "all of them."
He looked skeptical.
I scheduled him for a "career development conversation."
He stopped asking questions.
Microsoft sent a case study team.
They wanted to feature us as a success story.
I told them we "saved 40,000 hours."
I calculated that number by multiplying employees by a number I made up.
They didn't verify it.
They never do.
Now we're on Microsoft's website.
"Global enterprise achieves 40,000 hours of productivity gains with Copilot."
The CEO shared it on LinkedIn.
He got 3,000 likes.
He's never used Copilot.
None of the executives have.
We have an exemption.
"Strategic focus requires minimal digital distraction."
I wrote that policy.
The licenses renew next month.
I'm requesting an expansion.
5,000 more seats.
We haven't used the first 4,000.
But this time we'll "drive adoption."
Adoption means mandatory training.
Training means a 45-minute webinar no one watches.
But completion will be tracked.
Completion is a metric.
Metrics go in dashboards.
Dashboards go in board presentations.
Board presentations get me promoted.
I'll be SVP by Q3.
I still don't know what Copilot does.
But I know what it's for.
It's for showing we're "investing in AI."
Investment means spending.
Spending means commitment.
Commitment means we're serious about the future.
The future is whatever I say it is.
As long as the graph goes up and to the right.
Laravel Tip ๐
Easily share secure download links without exposing your S3 bucket with the temporaryUrl method.
Check how we can generate a temporary URL valid for 10 minutes in a clean and easy way in Laravel with the example TemporaryLink action. ๐ฅ
Laravel tip: `fake()->optional()` with PROBABILITY for NULLABLE fields.
See example?
The code of migration/factory and the result DB table.
0.3 means 30% chance of field with NOT NULL value.
@PovilasKorop@AshAllenDesign variable is useful for static values, method is useful for something more complex. maybe in the next page is only 1 result, so you override value to return all results instead. is is more about design pattern and giving new abilities.
There's a saying: "How you do anything is how you do everything".
So, adopt useful coding habits even when it's no big deal in some cases.
Even if you have 20 records, select only the fields you need.
Prevent yourself from being lazy to type a few words.
It's a good habit.
I'm excited to announce that Laravel has raised a $57M Series A in partnership with Accel.
I believe that Laravel is the most productive way to build full-stack web applications, and Laravel Cloud will be the platform for shipping those applications that this community deserves.