If there is one thing more frustrating than a production-breaking bug, it’s a bug in human mindset.

Lately, I’ve been sharing a lot of research-backed content aimed at keeping developers and professionals safe from scams, bad practices, and career traps. But instead of engaging with the data, a specific segment of the “half-baked” crowd has decided to focus on the wrong things.

I’ve started keeping receipts. Let’s debug these common mental errors.

1. The AI Hypocrisy

The most common comment I get now is: “Did AI write this?”

Screenshot: “Did you use AI to write this?” comment

Screenshot: “Did you use AI to write this?” comment

It’s the ultimate lazy critique. It’s a way for people to dismiss 15 years of industry experience because I choose to use modern tools to polish my delivery.

The Tractor Metaphor:

If you see a farmer using a tractor, do you tell him his harvest is “fake” because he didn’t use a hand-plough? No. You look at the quality of the crop.

In tech, tools like AI are the new tractors. If you aren’t using them to be more efficient, you’re falling behind. But don’t mistake the tool for the source. AI doesn’t have my experiences. AI didn’t fail the hundreds of projects I learned from. I did.

2. The “Cloud Chaser” Syndrome

Then there are the critics who call me a “Cloud Chaser”.

Screenshot: “Why are you a cloud chaser?” comment

First of all—English kathuko da (Learn the language). It is Clout, not Cloud. If you’re going to try and “bring someone down”, at least pass the spell-check first. If your linter is flagging your insult, it’s time to refactor your vocabulary.

But beyond the typo, the logic is flawed.

  • Scenario: I see a bad pattern or a scam.
  • Action: I document it and share it so YOU stay safe.
  • Response: “You’re just doing this for clout”.

If helping people avoid traps is “chasing clout”, then what is staying silent? Selfishness?

The Refactor

We live in an era where everyone has a microphone, but very few have something to say. If your only contribution to a conversation is to try and devalue the person speaking, you aren’t being “edgy”—you’re being a bottleneck.

We need to patch this “half-baked” mindset:

  • Engage with the logic, not just the tool.
  • Fix your own “code” before you try to debug someone else’s intentions.
  • Learn the difference between “clout” and “community”.

Let’s get back to building, not just bickering.