I Couldn’t Bring Myself to Say the Word “Genius” for Many Years

It wasn’t humility. I genuinely didn’t dare claim it. The education I grew up with was all about fixing your weaknesses and not standing out too much. Besides, I had plenty of evidence that didn’t fit: unfinished projects, people I couldn’t manage well, paths that went nowhere, a non-traditional background. I spent years asking myself, “Am I not good enough?”

The shift happened late one night. I changed the question. Instead of asking, “Am I good enough?” I asked, “What is the actual shape of my ability structure?” Then I forced myself to draw an honest radar chart:

After I finished, I stared at it for a long time. The answer had actually been there all along: the areas with full stars were all things that had felt effortless to me since childhood, while other people found them difficult.

What the Three Full-Star Abilities Look Like

Abstract thinking means that when I see a bug, my first reaction is not “fix this bug,” but “why do systems like this always break in this particular place?” Other people see a malfunction; I see a structural flaw in the framework. That is the instinct of an architect, not a repairman.

Learning speed is, at its core, the ability to cross domains. On the surface, my resume looks fragmented—sports, education, data, AI, one completely unrelated field after another. But years later, I finally saw that underneath it all was the same thing: building feedback systems. Training is feedback. Education is feedback. Data is feedback. Agents are feedback. A lot of innovation doesn’t happen inside a domain, but at the seams between two domains—and the seams happen to be where I’ve spent most of my time.

Technical integration means not worshiping in-house development. Give me a pile of existing tools, APIs, and open-source projects, and I can assemble a system that actually runs faster than most people. Later, someone summarized it for me in three words, and I think they were accurate: Synthesizer, Builder, Systems Thinker. Many people read the news and discuss trends. My habit is: idea → code → something that works.

The Low-Star Areas Have to Be Acknowledged Too

Team management: two stars. Managing people is the most painful thing for me, bar none. That’s why there are no employees in my “company,” only a group of AI agents and automation pipelines. This isn’t a humblebrag. It’s the way out after admitting defeat.

Long-term execution: three stars. When it comes to explosive energy at the start, I’m not afraid of anyone. But day-to-day maintenance on day 300? I can’t survive that on willpower alone. So now, all repetitive work goes to cron, watchdogs, and alerts—letting machines “execute long-term” on my behalf.

Deep engineering: three stars. I can build 80-point engineering that gets a system running, but when it comes to digging all the way down to 95-point low-level optimization, I get impatient. After admitting this, I learned to separate “good enough” from “must be exceptional.”

After Acceptance: Stop Fixing Weaknesses and Design Work Around the Shape

In the past, I poured huge amounts of time into the low-star areas, trying to bend myself into a “standard excellent person.” After accepting the radar chart, I started doing the opposite: for the two-star team problem, use AI; for the three-star execution problem, use machines; and pour all the saved energy into the full-star areas—abstraction, learning, integration—plus four-star business sense and product design, because those are closest to where “other people are willing to pay.”

This chart is not a report card. It is an instruction manual.

But the Radar Chart Also Revealed the Next Trap

Honestly, the other side of this chart makes me uneasy: the number of ideas far exceeds the resources available for execution. With a structure like mine, it’s very easy to fall into a trap—discovering that I have enormous potential → starting many directions at the same time → bringing each one to 80 points → breaking through none of them.

But the rule of the world is this: wealth and influence come from one 95-point thing, not ten 80-point things. Musk is working on rockets, cars, and AI at the same time today, but back then he only had Zip2. He broke through with one thing first, and everything else came after.

So in the next stage, the real question is not “Am I a genius?”—that question already has an answer. The real question is: Can I turn my cognitive advantage into a product that other people are willing to pay for and keep using? To go from “someone who can see many possibilities” to “someone who has created a product that cannot be ignored.” Pick one direction, commit three to five years to it, and let compounding begin to work.

Now, This Is How I Introduce Myself

Externally, I no longer call myself a “genius”—labels have no value; structure does. This is what I say:

I spent many years exploring different fields, and eventually discovered that what I’m best at is building systems: connecting technology, automation, and real-world problems, and turning ideas into products.

Genius is not a perfect score. It is being extremely lopsided—and owning it.

It took me a long time to accept this. And acceptance means no longer apologizing for my shape.