Hi, I’m Udip — I Build Technology That Makes Life a Little Easier

I grew up in India with a simple belief: technology should do more than impress people. It should help them.

That belief is why I started writing code in 2021. Not because I had a career plan. Not because someone pointed me toward it. Because I kept looking at the problems around me and thinking — someone should build something for this. Then I realized that someone could be me.

The Voice Assistant That Changed Everything

For my graduation project, I built MARK — a voice assistant I designed from scratch. Not a wrapper around an existing API. An actual voice-driven assistant with its own logic, its own responses, its own personality and precise security level for user’s data protection.

Out of over 20,000 student projects submitted that year, MARK was the only one to receive an official startup offer.

I’m not telling you that to brag. I’m telling you because it confirmed something I suspected: the gap between a project that works and a project that matters is smaller than most people think. The difference is usually just one person who cared enough to actually finish it — and who built it for a real reason, not just to pass a grade.

Building More Than Code

Around the same time, I was one of the founding members of the LEGO Smart City project at Humber Polytechnic. What started as a hands-on engineering challenge turned into a real lesson in systems thinking — how individual pieces connect, how decisions at one layer ripple through the whole structure, and how a team either builds together or falls apart.

Then, I took part in Capstone Project in Project Management and my team won by 1st rank.

Project management gets a bad reputation in tech circles. Developers often see it as overhead. I see it as the difference between a brilliant idea that ships and a brilliant idea that dies in a backlog. Knowing how to lead a team, define scope, cut what doesn’t matter, and keep people moving is just as critical as knowing how to write clean code. I’ve learned both. I use both.

Exploring the Edges

Not every project needs to solve a crisis. Some are about expanding what you think is possible.

I built a project that pulls live data from NASA’s cameras and tracks the Tesla Roadster floating through space — giving you real information about where it is and what’s around it. It’s a reminder that the universe is enormous and we’re only just beginning to explore it. That felt worth building.

I also built mental health tools during college — projects focused on making support more accessible, lowering the friction between someone who is struggling and someone who can help. They weren’t polished products. They were early experiments in the question I keep coming back to: how do we use technology to make someone’s day a little less hard?

Coming from India, I’ve seen what it looks like when access to the right tool or the right information changes someone’s life. It doesn’t always take a billion-dollar company. Sometimes it takes one developer who builds the right thing.

And Then Came F.R.I.D.A.Y.

If you’ve seen Iron Man, you know the AI. That’s what I’m building — for real, for myself, entirely from scratch.

F.R.I.D.A.Y. is a personal AI assistant with an entire agent network operating underneath it:

i. ATLAS for research

ii. FORGE for writing and building code

iii. PULSE for finance

iv. NEXUS for productivity.

F.R.I.D.A.Y. orchestrates all of it — deciding what each agent handles, reviewing their outputs, and bringing the answer back to me.

It has memory. It learns from conversations. It sets reminders, reads documents, searches the web, generates reports, and builds full applications on command. It understands images. It runs around the clock, even when I’m not actively using it.

I built it with real clean architecture — dependency inversion, formal interfaces, inner layers that never touch outer infrastructure. A codebase that doesn’t fight you when requirements change.

F.R.I.D.A.Y. isn’t a product yet. But it represents the clearest version of what I believe technology should be — something that works for you, understands your context, and quietly makes your life more manageable. Built by one person, for real use, not for a demo.

What Actually Drives Me

I want to use my skills to make a difference. Not in a vague, LinkedIn-caption kind of way — in a specific, practical, someone’s-day-got-better kind of way.

That’s what the mental health projects were about. That’s what MARK was about. That’s what F.R.I.D.A.Y. is about. The thread running through all of it is the same: what if technology actually made life a little easier for the person using it?

I’m from India. I’ve seen what it means when the right tool reaches the right person at the right time. I’ve also seen what it means when it doesn’t. That gap is where I want to work.

I’m four years into building. I’ve won competitions, received startup offers, shipped things that work, and broken things that had to be rebuilt from scratch. I’ve learned more from the failures than the wins.

Why I’m Writing Here

Most of what I know isn’t in any course or documentation.

It’s in the moment a 30-second shell command timeout kills a build that needed 5 minutes. It’s in the architecture decision that felt clever at 11 PM and revealed its flaw at 11 AM. It’s in winning a competition because your team actually trusted each other.

I’m writing it down — not as theory, but as real experience from someone still in the middle of building, still figuring it out, still driven by the same question I started with.

How do we build technology that actually helps people?

I’m Udip. Let’s figure it out together.