The Rejection That Changed Everything

In 2020, while the world was slowing down, my life was accelerating toward a single question: What now?

Growing up, the definition of success was handed to me. My parents saw me in a white coat—medicine was the respected, stable path. It's noble, I know. But inside? No spark. Just the weight of expectations. Meanwhile, I had a background in Electricity. I understood circuits, currents, power distribution—but I didn't know how to turn that into the independence I craved.

At 17, my definition of success was simpler than theirs: Independence. Be my own boss. Control my time. Build my own future. Like many peers, I looked at financial markets. Trading seemed like the shortcut—charts, leverage, and the promise of a laptop lifestyle. I spent hours daydreaming about financial freedom while my parents pushed the medicine narrative.

Coding? That wasn't even on my radar. My brother planted the seed once. He talked about programming like it was magic. I didn't get it. I Googled the definition: "Programming is the process of designing, writing, testing, and maintaining code that computers can execute." Cool. Still confusing. I figured I'd circle back later.

The Turning Point

Then came the rejection. Medical school said "No."

That rejection was the best thing that ever happened to me. It wasn't a closed door—it was permission to stop pretending. I looked at programming again, but this time with clear eyes. And suddenly, it clicked. Code wasn't just "telling computers what to do"—it was the universal bridge between everything I wanted:

• • Want to trade? Build bots to trade for you.
• • Want to help people? Build tools for doctors, teachers, anyone.
• • Want to be free? Work from anywhere, anytime.
• • Want to learn? Code forces you to think differently every day.

I traded the stethoscope for a keyboard. At first, I looked at Robotics—seemed like a natural evolution from Electricity. But I pivoted to IT instead. Not because it was trendy. Not because everyone was doing it. But because it was the only path that offered no ceiling.

No limits on what I could build. No permission required to start. No gatekeeper telling me I wasn't qualified. Just me, a laptop, and an internet connection.

Where I Am Now

This isn't the story of how I became a developer overnight. It's the story of how I found the path that felt right—even when everyone around me thought I was crazy for leaving medicine behind.

The goal hasn't changed: full-stack independence, automated finance systems, and building tools that solve real problems. The difference is that now I have the skillset to make it happen.

This is 000. The beginning of the log. Everything that follows is the journey from "What's programming?" to building real systems. Buckle up.