I didn’t start out wanting to be an engineer. I wanted to be a hacker — specifically, the kind my classmate described his older brother as, in the vague, impressive way 13-year-olds describe things they don’t fully understand. I didn’t know what “hacking” meant. I just knew I wanted to do it.
The Problem Was I Didn’t Have Wi-Fi
We didn’t have internet at home. A childhood friend did — his family had it set up right in front of our house — so most evenings I’d sit close enough to catch his signal, Android phone in hand, chasing tutorials on how to get onto networks I didn’t have passwords for.
Most of what I found was useless. Fake “hack any Wi-Fi in 5 minutes” videos, forum posts that led nowhere, tools that didn’t do what they claimed. I asked my father for a laptop. He said yes, on one condition: good grades in 8th grade. I held up my end. He bought one secondhand from a friend — 2GB of RAM, an 80GB hard disk, already a few years behind by the time I got it.
I installed Kali Linux on it and tried to run the tools everyone online said would work — deauth attacks, handshake captures with a tool called Fluxion that was supposed to be the “clean” way to get a Wi-Fi password directly from the user. In theory, it was elegant. In practice, my machine couldn’t handle it. It hung. It crashed. It overheated. I never once got it to work.
The Failure That Redirected Everything
At the time it felt like just a frustrating dead end. Looking back, it’s the most important failure in my career, because it’s what pushed me to stop trying to break things and start learning how they were built.
I got curious about the internet itself — not how to get onto a network, but how any of it worked underneath. That curiosity led me to Python in 9th grade. I don’t remember deciding to “learn a programming language” so much as stumbling into one, after watching a tutorial on building a simple game and thinking: I want to make this myself. I spent most of that year writing small scripts and automation projects, the unglamorous kind that don’t demo well but teach you how software actually behaves.
A friend who wrote blog posts online told me I could build a website too. I tried the drag-and-drop blogging tools he meant, and they didn’t interest me at all — it didn’t feel like building anything. So I went looking for the real version, and found out there was HTML, CSS, and JavaScript underneath all of it. By the end of 10th grade, I was a self-taught full-stack developer in every practical sense: I could take an idea and ship it end-to-end, with no one holding my hand through it.
What a Underpowered Laptop Actually Taught Me
None of this came from a course or a bootcamp. It came from hitting a wall — a laptop that was too weak to do the thing I originally wanted — and asking a better question instead of giving up. That’s the pattern that’s repeated through the rest of my career: when the direct path is blocked, there’s usually a more durable one next to it.
I couldn’t get a scholarship-funded internship after my first year of intermediate studies in Pakistan — attendance requirements made it impossible during the first two critical years. So I waited, kept building, and started professionally the moment I could, right after finishing intermediate. From there the work compounded: full-stack products, then a deeper pull toward Python and machine learning, until most of my time now sits at the intersection of the two — shipping AI systems that have to survive real users, not just a notebook demo.
Where That Leaves Me Now
Today, I’m the person in the room making architecture calls with CTOs, and increasingly the person figuring out where AI actually belongs in a company’s workflow versus where it’s just theater. The “critical problem” I care most about solving isn’t usually the flashy one. It’s the boring, repetitive bottleneck a team has quietly accepted as normal — the kind that’s costing them hours or headcount every week and nobody has gotten around to fixing. Replacing that with something reliable is, more often than not, the highest-leverage thing I can build for a client.
The People Who Made It Possible
I got the laptop because my father trusted a deal I made with him and kept it. My mother backed both of us the whole way. My siblings never once treated any of this as a phase. And it started, honestly, because a childhood friend happened to have Wi-Fi and a story about his brother that made a bored 13-year-old curious enough to start.
None of that shows up on a resume. All of it is the actual reason I do this work.