Sergio Ojeda

Nice community contribution to the query builder landing in next week's Laravel release. Define a manual order on a given column. 🔀

Times are changing. Developers are changing. Artisans are changing. christoph-rumpel.com/2026/3/the-age…

¿Cuántos devs deben andar con un poquito de ansiedad por todas las herramientas de AI (salen cinco por día más o menos) y con todos los artículos/posts de acá en tono: “TE VAS A QUEDAR SIN TRABAJO VAMOS A MORIR TODOS”?

🫠🫠

Estoy odiado

💡 If you have a database index, it's important to note that MySQL cannot use it with functions. The most common situation is date columns and date functions such as 'year' or 'month'. So instead of using 'year(paid_at)', use 'where between':

last night, I was skimming TanStack Query docs and went down a rabbit hole on its server-side usage with Next.js. What I found is a total gamechanger for performance. @tan_stack 🤯 >it's a pattern that combines server-side prefetching with client-side hydration to practically eliminate initial page load spinners. When you pair it with Server Actions for mutations, your app feels insanely fast. here's how it works, a Thread 🧵

Hey Laravel artisans, @laravel_idea is now FREE for all PhpStorm users! 🔥 Starting July 30, you can install and use the Laravel Idea plugin in PhpStorm at no extra cost. Enjoy the most productive #Laravel experience with PhpStorm! blog.jetbrains.com/phpstorm/2025/…

Me encanta este framework visual que se ha currado @SalamancaPeral

💅 You can now easily teach Claude Code our PHP / Laravel guidelines, so it will code with grace and style. spatie.be/guidelines/ai

Laravel devs, Are you still using Str::random() for passwords or building your own generator? 😅 There’s a better way — Str::password() 💪 Secure, customizable, and built right into the framework. Try it. You’ll love it. 🔐✨

The State Of Laravel 2025 survey has started! You can now participate to identify how the ecosystem changed over the past 12 months! Please RT for reach ❤️ stateoflaravel.com/participate?re…

Laravel tip. Use `exists()` and `doesntExist()` instead of `count()` for better performance! When you only need to check if records exist, these methods stop at the first match instead of counting all records. Link to the docs: #determining-if-records-exist" target="_blank" rel="nofollow noopener">laravel.com/docs/12.x/quer… #practicalLaravelDocs

🧠 @phpstorm users: You can customize the AI Commit Message action! I added Conventional Commits - now every commit starts with feat:, core:, etc. Cleaner history, zero effort. 💪

🔐 New guide: Laravel Sanctum Cookie Authentication Everything you need to implement secure SPA auth with Laravel Sanctum - from setup to production deployment, plus troubleshooting common issues. No more token management headaches! 🚀 laraveljutsu.net/blog/laravel-s…

A quick tip for performance tests. You can easily measure the execution time of a code-block with Laravel Benchmark helper ⏰ #laravel

Laravel devs, did you know? 👀 You can use Event::fakeFor() to scope event fakes to just part of your test. No more struggling with faked events killing real listeners. 🧪 Keep tests clean and fully reactive where it matters.

There's a new package called Laravel Zap. It's an event scheduler and is perfect for: - Events, appointments - Recurring tasks - Availability management - Conflict detections It's very promising.

Este plan de aprendizaje de AWS te guía en CI/CD, control de versiones e IaC. ¡Ideal para preparar la certif AWS DevOps Engineer! 👉 lnkd.in/gJT3zZts #DevOps #AWS #Certificación #CICD #IaC

Most people think upgrades are difficult and require lot of work and planning. There is a hack: * be consitent, * focused * and merge quickly This way you will reach maximum @rectorphp levels in single day 🚀 1) Start with this rector.php config: use Rector\Config\RectorConfig; return RectorConfig::configure() ->withPaths([ __DIR__ . '/public', __DIR__ . '/src', __DIR__ . '/tests', ]) ->withTypeCoverageLevel(0) ->withDeadCodeLevel(0) ->withCodeQualityLevel(0); 2) Increase all levels at once by 2-3 steps, based on codebase. Then re-run Rector and create PR ->withTypeCoverageLevel(2) ->withDeadCodeLevel(2) ->withCodeQualityLevel(2); 3) These PRs are easy to review, and joy to see the codebase grow 😊