Knowledge by execution.
A decade of work tends to leave a paper trail.
Hundreds of articles written. Dozens of products shipped. A few expensive lessons that didn't make it into any case study.
That's probably the best summary of how I work — obsessive about understanding things before I claim to know them.
Before the career, there was just a kid taking apart hardware, trying to understand how machines talked to each other. Got certified as a technician before I had a first real paycheck. That curiosity is the only thing that stayed constant through everything that came after.
The path followed a logic that only makes sense in reverse. Tech support. Marketing. Project management. Product. Consulting. No clear roadmap existed for most of that work in Pakistan when I started — so I drew one as I went. Learned product by shipping the wrong thing first. Learned business by getting it wrong deliberately, until right became obvious. A decade of that produces a certain kind of judgment you can't get from a course.
The work eventually split in two. One half: helping founders build what should exist, not what sounds good in a pitch deck. Discovery before development — that's the whole philosophy. The other half: helping people figure out tech and career without a playbook. The way I had to.
Neither half makes sense without the other. Both came from the same thing: seeing a gap and building something rather than complaining about it.
If I have an idea, it tends to have a .com at the end of it. Some are still standing. Most taught me something.
Both count. And there are probably a few in the queue as you read this.