On July 19, 2024, a seemingly routine software update became a global nightmare. CrowdStrike, a cybersecurity giant trusted by countless organisations worldwide, inadvertently released a faulty update that brought systems crashing across the globe. As someone who relies on technology daily, personally and professionally, I couldn’t help but feel a chill run down my spine as I watched the chaos unfold.
Let’s be clear: this wasn’t a cyberattack. It was an honest mistake, a “logic error” in the code that slipped through testing. But that’s precisely what makes it so terrifying. Imagine what a coordinated, malicious attack could do if a simple update can cause this much havoc.
If you think dumping a bag of charcoal into your Weber kettle barbecue is the key to BBQ nirvana, you’re about to get a wake-up call hotter than your overloaded barbecue.
Let’s start with a hard truth: your grill isn’t a dumpster fire, so stop treating it like one. That “more is more” mentality? It’s turning your steaks into hockey pucks and your wallet into a sad, empty leather pouch.
Let’s chat about everyone’s favourite corporate euphemism: the Performance Improvement Plan, or PIP for short. If you’ve ever been on the receiving end of one, you know it’s about as pleasant as a root canal without anaesthesia. But today, we’re going to peel back the layers of this bureaucratic onion and expose the tears-inducing truth.
First off, let’s dispense with the notion that PIPs are a well-meaning attempt by your company to help you improve. That’s as believable as your manager’s claim that they’re “not micromanaging, just checking in”. While some companies might have well meaning intentions, the truth is for most, once you’re on the PIP, you’re already gone.
Well, things are starting to make sense to me. Have you ever had a revelation that was confronting but then made complete sense? That’s where I am at.
I’ve been a programmer for 15 years and counting. I love what I do. Even after all this time, I still wake up excited and enthusiastic about my job and the industry. But over the last couple of years, coinciding with a big move and losing my usual support network, moving away from family; something shifted.
In this blog post, we’ll explore the concept of deep observation in TypeScript and learn how to create a deep observer using proxies. Deep observation allows you to track changes made to an object, including its nested properties, providing a powerful way to monitor and react to modifications in your data structures.
Understanding Deep Observation Deep observation involves monitoring changes made to an object and its nested properties. When a property is modified, whether it’s a top-level property or a deeply nested one, you can capture and respond to those changes. This is particularly useful when working with complex data structures where changes can occur at various levels of nesting.
With the release of Aurelia 2 Beta 15, there are some important changes to be aware of regarding decorators. This update brings Aurelia 2 into compliance with the Stage 4 TC39 decorators proposal, resulting in significant differences in how decorators work compared to previous versions.
One notable change is that inline decorators for injection on constructors are no longer supported. For example, the following syntax is no longer valid:
constructor(@IApi readonly api: IApi, @IRouter private router: IRouter) { } Instead, to handle injection, you can define a class property and use the resolve function from the aurelia package. Here’s an example:
Let’s face it: React’s popularity is a classic example of being in the right place at the right time.
When it first hit the scene, the web development world desperately needed a saviour. Developers were drowning in the complexities of AngularJS, with its notorious digest cycle and performance issues that made building with Angular a nightmare. Along came React, with its fancy virtual DOM and declarative approach, and suddenly, everyone was singing its praises.
It’s a question that has haunted the minds of philosophers, scientists, and conspiracy theorists for ages: are we truly native to Planet Earth, or could we be the extraterrestrial visitors we’ve been searching the stars for all along? While it may sound like an outlandish theory from the depths of science fiction, there are some astonishing pieces of evidence that suggest the possibility of humans being the real aliens. Buckle up and prepare to have your worldview shattered as we dive deep into this mind-bending hypothesis.
Remember the 1990s when Microsoft was the big bad wolf of the tech world? Their iron-fisted control over the PC ecosystem led to a massive antitrust case and made Bill Gates public enemy #1 for a while.
Well, it looks like Apple didn’t learn from Microsoft’s mistakes because it’s now following the same playbook with the iPhone. And surprise, surprise—the antitrust cops are knocking on Cupertino’s door.
Glorious leader Tim Cook
JavaScript has been around for over 25 years, yet it’s more popular and dominant than ever. Some love to hate it, others grudgingly put up with it, but let’s cut through the bullshit – JavaScript has firmly cemented itself as the one true king of programming languages. And its reign looks set to continue for a long time yet.
First, there’s the ubiquity. JavaScript is fucking EVERYWHERE. It runs in every browser on every device. It’s the default language of the web. And with Node.js, it’s busted out of the browser to conquer the server side, too. You can’t swing a cat without hitting some JavaScript. It’s like the Starbucks of programming – inescapable but also weirdly comforting in its consistency.