A while ago, a guy who wanted to rewrite the entire system of the company we worked at from Laravel to NestJS with TypeScript told me, 'Ah, TypeScript is so much better than PHP because you can enforce types as parameters, while PHP allows anything.' Well... I hope this post

It's 2025, and you still think PHP is just about WordPress? Come on, step out of the bubble. Do some research. With all the AI tools available: Bing, Google, OpenAI, Gemini. There’s no excuse for being uninformed. Take five minutes, install something, and test a Hello World. Back

I don’t consider myself a framework/language fan, but I already had contact with NestJS, Node with Express, Symfony (PHP), Slim (PHP), AdonisJS, Spring Boot (Kotlin), NextJS,/NuxtJS (frontend stuff), Delphi 10 (long time ago), and pure Python (long time as well). Many of these

Sending stupidity right back where it came from: JavaScript wasn't made for backend systems. TypeScript isn't compiled; it just turns back into JavaScript. Serious systems don't use JS on the backend. Sounds familiar? Exactly. That's how people see you when you throw out

Explaining: If you ignore the evolution of things, your opinions may seem uninformed. As a Senior PHP Engineer, I often see misguided views about PHP, overlooking its growth in OOP, strict typing, and modern runtimes like Swoole and RoadRunner. So I've used JS and said foolish

Murphy's Law. Just lost 2 hours of work. Was recording a video about dependency injection and dependency inversion using #php. My mic stopped working, so I'm going to buy a new one. Suggestions? In the meantime, I’m going to cook up an article about it that I’m sure almost no one

Ever mixed up Dependency Injection and Dependency Inversion? You're not alone! One controls how dependencies are provided, the other ensures you rely on abstractions, not implementations. Here’s the article I wrote about the subject: sahdo.io/dependency-inj…

In many architectures, unit tests are preferred over integration tests, like testing Use Cases, Services or Domain Entities. Correct me if I'm wrong, but by definition, the moment your class interacts with the database, you're dealing with an integration test, right? Your Class

Wanna avoid those 5k tests taking 2 hours to finish? Start writing more unit tests and fewer integration tests. Testing is so good when you can actually mock the persistence layer, light, efficient, and fast. #UnitTest

Have you ever encountered this error when using Laravel Queued Jobs with Amazon SQS for example? 𝑰𝒏𝒗𝒂𝒍𝒊𝒅𝑷𝒂𝒓𝒂𝒎𝒆𝒕𝒆𝒓𝑽𝒂𝒍𝒖𝒆 (𝑺𝒆𝒏𝒅𝒆𝒓): 𝑶𝒏𝒆 𝒐𝒓 𝒎𝒐𝒓𝒆 𝒑𝒂𝒓𝒂𝒎𝒆𝒕𝒆𝒓𝒔 𝒂𝒓𝒆 𝒊𝒏𝒗𝒂𝒍𝒊𝒅. 𝑹𝒆𝒂𝒔𝒐𝒏: 𝑴𝒆𝒔𝒔𝒂𝒈𝒆 𝒎𝒖𝒔𝒕 𝒃𝒆 𝒔𝒉𝒐𝒓𝒕𝒆𝒓

Ok, the starter kits are great... Inertia + #Vue (or #React). Imagine you're in a hurry to test an MVP and get your first 10 clients. Dude, you have a dashboard with #Tailwind, Vue or React, password reset, and profile management. Imagine this for someone who knows so little

Dependency Inversion Principle... Why It Matters? The Dependency Inversion Principle (DIP) is the foundation of architectures like Clean Architecture, Ports and Adapters, and Layered Architecture. Understanding it helps you write more flexible and maintainable code. I just

Looks like opinions are shifting! Shoutout to all the #PHP devs who stood their ground, mastered their craft, and became true specialists without fear. Now, you're the protagonist, while they’re the ones changing sides now. It's VERY, VERY important to acknowledge the amazing

Testing Laravel Cloud with Laravel 12, Inertia & VueJs 3. I just set up a full-stack app using Laravel Cloud, Laravel 12, Inertia, and VueJs 3 in only 18 minutes! #Laravel12 #InertiaJS #VueJs3 #PHP

Excited to share that I’ve started a new position as a Senior Software Engineer at Leasecake ! I’ll be working with microservices built with PHP and Laravel, AI-powered apps, Vue.js, and more. Looking forward to this new chapter! 🚀

💡 MVP vibes. Currently building an integration between the BMGBank API and WhatsApp (Meta) using a Laravel Framework+PHP 8.3 API. ✅ Applied the Strategy Pattern to handle different flows of messages 🔜 Planning to implement Chain of Responsibility to manage each message

𝗞𝗶𝗹𝗹𝗶𝗻𝗴 𝗣𝗛𝗣 𝗶𝗻 𝟮𝟬𝟮𝟱, 𝘁𝗵𝗲 𝗿𝗼𝗮𝗱𝗺𝗮𝗽: To “kill” PHP, you’d need to destroy: 🏛️ The PHP Foundation 🛒 Adobe Magento 🧱 Frameworks like Symfony, Laravel, Slim, Hyperf, CodeIgniter, Laminas, and others 💸 Accel, which invested $57 million in Laravel 📦

I’m testing right now and really appreciated their philosophy. It offers a refreshing approach to PHP development: simple, modern, and thoughtfully designed.