Have you ever wanted to get rid of that content editor block in your custom post types? You know, that big empty space sitting there taking up room when you don’t need it? This is how you can hide it without using plugins.
The Solution All you need is ONE line of code. Just add this to your theme’s functions.php file:
remove\_post\_type\_support('your-post-type', 'editor'); Swap out ‘your-post-type’ with whatever post type you’re working with. For example, if you’ve got a custom post type for reviews, you’d use:
The WordPress community is in turmoil, and at the center of the storm stands Matt Mullenweg, once hailed as a visionary but now increasingly viewed as an open-source dictator. His recent actions have exposed the alarming centralisation of power within WordPress and raised serious questions about the project’s future.
Mullenweg’s conflict with WP Engine has laid bare the ugly truth: despite its open-source ethos, WordPress is effectively controlled by one man. His decision to temporarily ban WP Engine from accessing WordPress.org resources not only disrupted countless websites but also demonstrated how easily he can weaponise his position against perceived threats.
Aussie Broadband has just unveiled a new line-up of NBN plans that Aussie power users and professionals have been asking for a while. Dubbed the “PRO” plans, these offerings cater to those who need high download speeds and larger upload capabilities—something that has been sorely lacking in many NBN plans to date.
The plans include:
• NBN 250/100 at $139 per month
• NBN 500/200 at $169 per month
• NBN 1000/400 at $199 per month
AI tools are incredibly useful. They assist with debugging, problem-solving, and even serve as a high-tech rubber duck for discussing problems. However, there’s a growing trend that I’ve noticed both in myself and within the developer community.
The Comfort Zone Trap It’s easy to fall into the trap. You encounter a roadblock, and instead of working through it or consulting the documentation, you ask ChatGPT or Claude. Problem solved instantly. While it feels efficient, it raises a question: are we compromising our long-term development skills
The TypeScript team has unveiled the beta version of TypeScript 5.6, and it’s brimming with features designed to make our lives easier.
Catching Logical Errors Early: Disallowed Nullish and Truthy Checks One of the standout features in TypeScript 5.6 is the stricter handling of nullish and truthy checks. Previously, TypeScript would quietly accept certain logical errors, leading to potential bugs that were hard to catch. Now, the compiler flags expressions that always evaluate to a specific boolean value, such as:
Look, we’ve all been there. You’re knee-deep in JavaScript code and suddenly have this brilliant idea: “If I just tweak this bit here, surely it’ll run faster!” Before you know it, you’re down a rabbit hole of micro-optimisations, convinced you’re crafting the most efficient code known to humankind.
The Optimisation Itch
It’s tempting. The thought that with just a few clever tricks, you can make your code zoom along at lightning speed. But here’s the kicker: more often than not, these early optimisation efforts are a bit like rearranging deck chairs on the Titanic. They might make you feel productive, but they’re not addressing the real issues. Because if you haven’t even built your app yet, what are you optimising?
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.