ADHD or Just a Different Operating System? The Radar vs. Engine Metaphor

You’ve probably spent years beating yourself up for not being able to stick to a rigid schedule. You buy planners, download Pomodoro apps, and try to "hustle" like everyone else—only to burn out in three days and feel like a massive failure. You label yourself lazy, unmotivated, or just undisciplined.

I did this for most of my 20s.

As an indie founder and developer building my system, BaziLens, I used to feel incredibly guilty whenever I couldn't write code for 8 hours straight. I would spend three days staring out the window, reading obscure Wikipedia articles, and seemingly doing absolutely nothing. Then, in a manic 4-hour burst at 2 AM, I would solve a massive architectural problem that would have taken a week of "normal" work.

I thought I was broken. But as I dove deeper into the ancient framework of Four Pillars of Destiny (BaZi), I realized I wasn't broken at all. I was just trying to run the wrong operating system.

It basically splits people into two broad categories when it comes to how we process reality and manage energy: The Engine and The Radar.

In my observational framework, these two operating systems map beautifully to specific Life Roles.

The Engine runs on a linear track. Engines need a clear destination, a rigid schedule, and predictable fuel. They thrive on routine. These are the people who can wake up at 5 AM every single day, hit the gym, and grind out work on a spreadsheet for 8 hours straight without losing momentum. To an Engine, productivity is measured by distance covered over time. In the Four Pillars system, these are often people heavily dominated by The Manager (Officer) or The Operator (Wealth) stars. They are built for structure, rules, and steady resource accumulation.

The Radar, on the other hand, doesn't run on tracks; it absorbs signals. Radars are designed to sit still, scan the horizon, and process massive amounts of invisible, unstructured data. They are hyper-vigilant, pattern-recognizing machines. To a Radar, productivity isn't about moving forward constantly; it's about synthesizing complex, seemingly unrelated data into a sudden, brilliant insight. In our framework, these are people dominated by The Creator (Eating God / Hurting Officer) or The Strategist (Indirect Resource). They don't follow rules; they bypass them to build entirely new systems.

The modern self-improvement world is built by Engines, for Engines. It glorifies the daily grind and the unbroken streak. So when a Radar tries to operate in an Engine's world, the system inevitably crashes.

When you force a Radar to grind out 8 hours of repetitive tasks, it’s like using a billion-dollar military satellite to tow a broken car. It will overheat, shut down entirely, and you will look "flaky" to everyone else.

Recently, I shared this metaphor publicly and received an overwhelming response. One user, an IT support professional we’ll call "Alex," reached out to share an experience that perfectly illustrates this dynamic.

Alex had been doing IT support for years and noticed how some colleagues could effortlessly grind through support tickets all day long. They had a steady, predictable rhythm. Alex, however, would feel completely drained and mentally exhausted after just two hours of repetitive, straightforward tasks.

Alex felt defective. But then, there would be a massive system failure. Something weird would break that nobody in the department could figure out. While the "Engines" were stuck going through their linear checklists, Alex would suddenly connect the dots between completely unrelated system issues and solve the problem faster than anyone expected.

Alex's brain wasn't broken; it was just a Radar. That IT support environment—clearing a ticket queue—was a factory built for Engines. But that ability to connect the dots on a weird, unsolvable system break? That is the exact ROI of a Radar. Engines keep the lights on, but Radars fix the actual grid when it goes down.

In another instance, someone challenged the idea, saying that staring out the window for three days before starting a project was just pure laziness, and that true experts put in 10,000 hours of focused work.

They were absolutely right that you have to put in the reps. But to a Radar, 10,000 hours isn't a linear assembly line. It looks "random" from the outside—obsessive deep-dives into multiple disciplines to connect invisible dots. Steve Jobs auditing a calligraphy class looked like "doing random things" to an Engine. Later, it became Apple's typography.

If you suspect you are running a Radar OS, you need to stop trying to install Engine software. It will only corrupt your files. Here is what actually works:

Your output is fundamentally non-linear. You are paid (by life, by the market, or by your employer) for your synthesis and creativity—not your sweat. Measure your days by the quality of the connections you made, not how many hours you sat chained to a desk.

That staring-out-the-window time you feel intensely guilty about? That’s not laziness. That is your system defragmenting the hard drive and compiling the massive amounts of data you've absorbed. If you constantly interrupt this process with guilt ("I should be working right now"), the compiling never finishes, and you end up chronically exhausted.

You will work in chaotic sprints of hyper-focus followed by periods of necessary hibernation. Stop trying to smooth out your energy curve into a steady, boring line. Ride the bursts of manic energy when they come, and unapologetically rest when they fade.

Building BaziLens in public has taught me that the biggest trap for a Radar is self-judgment. If you don't learn how to focus your radar, you just spiral and get nothing done. That's exactly why we need to figure out our "operating system" early.

Once you know you're a Radar (or dominated by The Creator stars), you can set boundaries to protect your time, instead of just feeling like a broken Engine. The Four Pillars framework doesn't tell you what to do; it just gives you the ultimate permission to stop trying to be an Engine when you're clearly built to map the territory.

Let the Engines pull the train. You’re here to chart the course.

Curious about your own operating system? If you want to move past just your Zodiac animal and discover whether you are built to be an Engine or a Radar, try running your chart through the BaziLens calculator to find your true Day Master and Life Roles.