Fazal

Growing up, the internet was a rabbit hole I never wanted to climb out of. Every program, every blinking cursor, every page that loaded raised the same question: how does this actually work? From painting pixels in MS Paint to sending messages across the world through Yahoo Messenger, technology felt less like a product and more like a mystery worth solving. I studied Electrical & Electronics Engineering — the circuits-and-signals kind — which turned out to be the long way around to the thing I actually wanted to do.

That thing was building software. Not as a hobby, but as a craft. I spent years learning how production systems actually behave — the invisible machinery that runs quietly in the background, under load, without anyone noticing (because when you do notice it, something's gone wrong). Backend systems, distributed architectures, databases — I got good at it. Occasionally great at it.

Then AI came along and made everything more interesting. Not the demo version — the real engineering problem of making AI actually useful in production. How do you build platforms that let entire teams ship AI products, not just experiments? How do you design systems that are reliable, observable, and honest about what they don't know? That's the problem I've been wrestling with, and the one I find most worth solving right now.

Away from the keyboard, I read too much trivia and compete in quizzes with unreasonable enthusiasm. I think the same curiosity that makes someone good at pub trivia also makes them good at debugging a system at 2am — both require holding a lot of context, following threads, and refusing to accept "I don't know" as a final answer.