The curious case of building.

The wall between having an idea and building it just came down.

Since then, I’ve been building for the tech. Literally: forthe.tech.

For decades, people with ideas hit the exact same wall. You could see the thing with total clarity in your mind. You knew how it should feel, what problem it solved, and who needed it. But you couldn’t write the syntax, configure the servers, or hire a team of six engineers to wire it together. So the idea died quietly in a notebook.

Now you can build it.

You describe the problem, you guide the intelligence, and the software gets built. It feels like magic, and we are extraordinarily lucky to be here to witness it.

The Deluge and the Delusion

It is also impossible to keep up with.

Something “revolutionary” launches every single morning. By the next afternoon, it is already yesterday’s news, replaced by another drop that promises to rewrite how humans think and work.

Entire industries get disrupted by a single feature release. Products that took small companies five years of sweat to construct become a throwaway checkbox in the next model update. We watch cycles of panic layoffs across tech, followed by sheepish rehiring six months later once the compute bills roll in and the sloppy, unguided code breaks in production.

Watching from the sidelines isn’t enough. If you just watch, you become cynical.

But being online twenty-four hours a day chasing every benchmark, model leak, and changelog isn’t enough either. That isn’t building; it’s consumption dressed up as research.

So I filter.

The Filter in Dubai

Around a demanding operations job and family life in Dubai, my time is finite. I don’t have twenty hours a week to scroll through demo videos.

I follow what ships, but I filter the deluge through people who see further. I’m fortunate to share an office with leaders like Sathish Jeyakumar and Chakir QATAB, and to trade notes inside Uttam Gupta’s community. When you put a new tool in front of seasoned operators and engineers, the hype evaporates fast. Between them, I can separate genuine step-changes from marketing noise.

And once the noise is gone, I don’t just read about the new tools.

I test them.

The Curious Case of Building

The only way I know how to learn is to build.

When a new capability drops, I don’t read the documentation cover-to-cover and theorize. I open an editor, pick a problem that is irritating me or someone near me, and see if the tool can actually solve it.

I build because I am insatiably curious about the possibilities:

• What happens when a non-coder is handed the leverage of a senior software team?
• What happens when multi-agent systems stop being an academic paper and start handling real workflows?
• What happens when you strip away roadmap committees, venture timelines, and product-positioning decks, and just build because the friction exists?

I’ve been building random things across different stacks and frontier models for a while now. Some worked beautifully. Some broke in production in four different ways before lunch.

For two years, all of this lived scattered across local directories and private folders. If someone asked what I did, I would default to describing my day job, leaving this entire body of exploration hidden.

So I started documenting it all in one place: forthe.tech.

For the tech. For better or worse. Not as a portfolio of polished SaaS launches, but as an open field laboratory of what happens when curiosity meets frontier tools.

The Grounding Truth

Here is the one rule that keeps me honest while exploring this frontier:

Nobody values how complex your build was. Nobody cares what prompt scaffolding you chained together or what model size you ran underneath. The compute doesn’t matter to the person on the other end.

They only care whether their Tuesday got ten percent easier. They only care if the friction disappeared.

The wall is down. The possibilities are wider than they have ever been in our lifetime.

Keep building. Stay curious. Till it’s over.