Clem Blanco

Software engineer @infomaniak • Open source and Laravel enthusiast

[Wendell Adriel @wendell_adriel]

Yesterday, I published a new article on my blog about the Eloquent Query Classes pattern.

I received good feedback about it, and some people reached out to me asking if I had a skill for it.

I just released a skill for it that you can find at the link below! 👇

[Clem Blanco @clemblanco]

@andrebreia Been there. I was lucky enough to bounce back fairly quickly. I saw you on https://t.co/TxQEXKsZPL we're not far away from each other. DM me if you wanna hangout at some point. Hang in there.

[Jason McCreary @gonedark]

`git-trim` been getting some love lately. Just tagged a new release. This does a better job of handling Git Worktrees - which have renewed use from AI workflows.

https://t.co/32aItQ4QUI

[Swiss Laravel Association @swisslaravel]

Tomorrow we're back in Geneva at the Infomaniak offices. Doors open at 18:00.

Yves Engetschwiler will share how working with AI daily has changed his workflow — and sometimes challenges your confidence in your own skills.

→ RSVP: https://t.co/gQWuKtg6y4

[Stephen Rees-Carter @valorin]

Laravel Moat is a new tool that assesses the security posture of your GitHub repositories and recommends ways to tighten the controls protecting them.

https://t.co/YojYck7HS3
https://t.co/royWCmiQ64 #Laravel

[Clem Blanco @clemblanco]

@MrPunyapal And if you are doing a lot and need abstraction, start small. Maybe a string backed Enum, a Scope and an Action class is enough to start with.

[Punyapal Shah @MrPunyapal]

One underrated Laravel skill:

knowing when NOT to create another abstraction.

Not every problem needs:

- a service
- a repository
- a trait
- 4 interfaces

Sometimes a small clean class is the best architecture.

[Clem Blanco @clemblanco]

@joshcirre Macros are yet simple but give you endless opportunities to extend things.

[Clem Blanco @clemblanco]

Truth.

[ThePrimeagen @ThePrimeagen]

There has been no greater blessing in my life and no greater purpose driver than being a father

10 out of 10 would recommend

[Freek Van der Herten @freekmurze]

My colleague Nick wrote a good post on using AI for reading code, not generating it.

Instead of pointing AI at the “generate more code” problem, he used it to understand what was already there: map the codebase, describe the data model, trace dependencies, and surface hidden assumptions.

That feels like a very practical use of these tools.

[Luke Kuzmish @cosmastech]

Pao now belongs to the @laravelphp Github org. Nice work @enunomaduro 🥳 I just added it to my work's monorepo.

Now to get rector support added 😅

[Sadique Ali @apnahive]

Most PHP developers don't hate writing code.

They hate writing tests for it.

Pest PHP 3 is quietly changing that — and it's the most developer-friendly testing framework the PHP ecosystem has ever had.

Here's what's new in version 3 👇

🧬 Mutation Testing (built-in)
Not just "did this line run?" — but "if I introduced a bug here, would your tests catch it?" Run --mutate and find out.
👥 Team Annotations
Tag tests with ->team('payments') and filter CI runs by team. Finally, large codebases have a way to own coverage.
🏗️ Architecture Testing
arch()->preset()->laravel() enforces your structural conventions automatically. No more README rules that nobody follows.
⚡ Parallel Testing (improved)
Smart isolation across processes. 60-80% faster CI on large suites.
✅ Richer Expectations
toHaveStatus(), toBeIn(), toContainOnlyInstancesOf() — assertions that read like documentation.
And the core syntax is still the best part:

it('calculates tax correctly', function () {
expect(calculateTax(100, 0.2))->toBe(20.0);
});

That's it. No class. No boilerplate. No noise.

Pest runs on top of PHPUnit — so your existing tests keep working. Migration is incremental and low-risk.

If testing in PHP ever felt like a chore, Pest 3 is worth a serious look.

📖 Full breakdown on the article.

#PHP #Testing #PestPHP #Laravel #SoftwareDevelopment #DevExperience #CleanCode https://t.co/hkj1RnfW3a

[Wendell Adriel @wendell_adriel]

Just released a new package:
🛡️ Laravel Idempotency

It provides an HTTP middleware for Laravel (with an attribute for those who prefer it) for making routes Idempotent.

It also ships with two commands for listing and clearing Idempotency caches, and of course, a Boost AI skill!

Check the package and the docs in the link below, and leave a star to support the project! 👇

[Joe Tannenbaum @joetannenbaum]

We gave the Laravel installer a bit of a glow up 🧑‍🎨

The output is now far more concise by using the new 𝚝𝚊𝚜𝚔() helper from Laravel Prompts

Still want the full output? Just add -𝚟

It's a good day to 𝚕𝚊𝚛𝚊𝚟𝚎𝚕 𝚗𝚎𝚠 🤘

[Wendell Adriel @wendell_adriel]

Read it here:

https://t.co/K6mO1J17rZ

Some time ago, you gave me the idea @danielhe4rt!

It took some time to get it the way I wanted, but here it is! 🫶

[Clem Blanco @clemblanco]

@enunomaduro If you were doing something wrong, Nunonation wouldn't be a thing. Of course you can't please everyone and that's okay. We're used to this with open source anyway. Haters gonna hate. Keep up the good work man. 💪

[trish @TrisH0x2A]

wise words from the best systems engineer I've worked with:

"two things that make code actually maintainable:

1. reduce the layers a reader has to trace
2. reduce the state a reader has to hold in their head"

applies to every codebase. always.

[Clem Blanco @clemblanco]

@enunomaduro @0x15f @taylorotwell That is insane!

[Tim MacDonald @timacdonald87]

Some generic off-the-cuff test suite performance tips that helped cut a suite's runtime be 60%.

Maybe they'll be useful to you too.

[JustSteveKing @JustSteveKing]

I published an Engineering Career Framework. A clear, honest guide to every level from SE1 through VP.

No vague language. No moving goalposts. Just what’s expected at each level and what good looks like.

A few things I was deliberate about:
→ SE3 is a valid long-term destination. Not everyone needs to keep climbing.
→ IC and management are separate tracks. Neither is more senior.
→ SE4 has different "shapes" - there isn’t one archetype of a senior engineer.
→ Timelines are concrete, not "when you’re ready."

Hope it’s useful for engineers thinking about their own progression, and for managers trying to have better career conversations.

https://t.co/udZLxwVjvz