James Q Quick

🐘 "PHP Grew Up. Did You Notice?" PHP in 2024 was a completely different language than the one you're making fun of. I get it. The old jokes write themselves. mysql_query(). Global state everywhere. $_POST['whatever']. I lived through that era too. I have the scars. But here's the thing, while a lot of us moved on and kept dunking on PHP from the sidelines, the language kept shipping. Quietly. Consistently. Every year. PHP 8.0 brought named arguments, match expressions, and union types. PHP 8.1 brought enums, fibers, readonly properties, intersection types. PHP 8.2 brought readonly classes, new random APIs, and a serious cleanup of the deprecation backlog. That's not maintenance. That's a language that's actively evolving. Over the next few weeks I'm going to walk through the features I wish I'd paid attention to sooner. Not with docs-style explanations, just real examples of how they changed the way I actually write code day to day. If you still think PHP is stuck in 2009, stick around. I think you'll be surprised. Feature 1: Readonly Classes You were writing 3 files to do what one keyword now does For years, making a truly immutable object in PHP felt like a punishment. You'd write a class, make all the properties private, write a constructor, write a getter for every single property, add a docblock, hope nobody on the team did something creative with reflection... and then do it again for the next DTO. Every. Single. Time. PHP 8.2 just added readonly class and I genuinely felt a little embarrassed about how much boilerplate I used to write. The readonly modifier on the class means every single property is automatically readonly. No setters. No accidental mutation. No defensive getters. You can still make properties public because nothing can change them after construction anyway. This is the kind of feature that makes your DTOs, value objects, and API response models genuinely pleasant to write. I've refactored probably a dozen classes since this landed. Each one got shorter. None got worse. What pattern do you use for immutable data transfer objects? Still doing the old approach? #PHP #PHP82 #WebDevelopment #CleanCode #PHPGrewUp #BackendDev #BackendDevelopment

22

I know I run core tech bootcamps, but let’s be real, not everyone will be a techie or work in tech. And that’s okay. You don’t have to punish yourself just because tech is trending or because everyone around you is talking about coding, cybersecurity, or data analytics. If learning tech makes you frustrated, unhappy, or even depressed, you probably won’t complete that journey. And trust me, forcing it won’t magically make you love it. Instead of dropping what you actually love to chase something just because of peer pressure, why not learn how to use tech to amplify what you're already good at? If you love fashion, you don’t have to code an app, learn how to use AI tools like Clo3D, Canva AI, or Midjourney to create stunning outfits patterns and designs, or how to use digital marketing to rightly position yourself on platforms where those who need your services would find you. If you’re passionate about teaching, don’t force yourself into software engineering, use AI tools to make your lessons more engaging. If you enjoy running a business, you don’t need to become a data analyst, just learn how to use analytics tools like Excel spreadsheet or Google sheet to track your sales and improve marketing. This is exactly why, in our Data Analytics bootcamp and other tech training programs, we don’t just teach our students tech skills, we show them how to use these skills and tools in their existing careers. Instead of pushing them to chase core tech roles, we help them integrate tech into what they already do. Tech isn’t just about coding; it’s a tool to push what you’re already doing and make it big. So, instead of stressing over what doesn’t excite you, find a way to make tech work for you. That’s the real game-changer. #techwithini #techclaritycoach

33

2 Comments

I used to think senior engineers had the entire internet memorized. Seriously. Every library, every framework, every obscure command line flag. My goal was just to absorb it all. Then I started watching the *actual* senior engineers around me. They weren't walking encyclopedias. They were professional 𝘀𝗶𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝗿𝘀. They ask more questions than they answer. They delete more code than they write. They obsess over the "why" before they ever touch the "how." It turns out seniority isn't about knowing 1,000 niche solutions. It’s about having the judgment to pick the right *one* and ignore the other 999. 💡 It’s a lesson we apply every day. It's easy to build a tool with 100 features, but we're trying to build one at HireZapp that just does the few things that *actually* fix the hiring chaos. For all the senior devs out there, when did you realize your job was more about subtraction than addition? #hiring #recruiting #hirezapp #engineering #softwareengineering

4