Very early in my career, I became the lead break/fix technician in a small IT department. I didn’t get the role because I knew someone or played office politics well (because, for full transparency, I still don’t). I got it because I showed up with a positive attitude, could troubleshoot problems effectively, and genuinely cared about doing the work well. It felt like a natural progression, and I was proud of it. It’s a pattern that’s followed me throughout my career. Get an individual contributor position and eventually move into leadership. by Scott Keck-Warren
Welcome back to our journey into resilient PHP applications. In Part III, we focused on traffic resilience with **HAProxy** and saw how a healthy edge keeps bad nodes out of rotation. That only helps if the user can land on any healthy node and keep working. If their session lives on the server that just died, the infrastructure may be healthy while the user still experiences an outage. by Wendell Adriel
Alright, so we’ve cleaned up our data, and now it’s time to start building the actual brains of our machine learning system. We’re talking about neural networks – the digital equivalent of brain cells that can learn, adapt, and make decisions. But before we build a full network, we need to understand the fundamental building block – the perceptron. by Christopher Miller
I woke up to an email no developer ever wants to see. AWS Support, subject line in bold – my SES account was under review. High bounce rate. Abuse reports. The kind of message that makes your stomach drop before your coffee’s even brewed. by Eric Mann
Hello friends, and welcome to another Yelling At Clouds column. I am continuing my series on testing patterns in the hopes of giving you the skills to recognize when a specific pattern will solve your problem. by Chris Hartjes
There’s a particular kind of pain that comes from inheriting an API where the documentation says one thing, the code does another, and the consumers have long since written their own internal notes to track the difference. You stop trusting the spec. You start reading the source directly. The documentation becomes decorative. by Steve McDougall
When you see an odd AI response, what caused that response? Is it a hallucination, or something else? A detective might call this “figuring out the motive.” Learning to reason from effect back to cause is an important skill for working alongside AI. This month, we learn this reasoning skill. Beginning next month, we will be practicing and gaining mastery of this skill. by Edward Barnard
Each release of PHP bring new capabilities to enhance our capabilities or reduce boilerplate code. PHP 8.4 introduced property hooks for handling getting and setting object properties without having to create a ton of getter and setter methods. This month, we’ll see how we can add these features to our Spacetraders client. First, we upgrade Valinor, update Docker to support PHP 8.4, learn how property hooks work, and then use Rector to automatically add them to value objects. by Oscar Merida
I spent hours debugging a problem that came down to a single character. A function was modifying an array that should have been unchanged. I checked everything from the function logic, the calling code, to the data itself. Everything looked correct. Finally, I spotted an ampersand in the foreach loop from code I’d written months earlier and forgotten about – hours for one character. by Marian Pop
Everyone is talking about AI. With my usual cynical developer hat on, it took a long time to really embrace what was being offered. The early offerings, for example, had internet information cut-off dates. by Jim Seconde
Leave a comment
Use the form below to leave a comment: