The True Code Of A Complete Engineer

I Accidentally Found the Best Career Accelerator in Tech

A stable job kept me comfortable. A simple OTT side project taught me more about ownership and growth than years of routine work did.

Gaurav Sharma

05 Jul 2026 • 6 min read

Pencil sketch illustrating a software engineer leaving the comfort of a stable job to build a pet project, representing career growth through side projects and hands-on learning.

A blog series by Gaurav Sharma: The True Code of a Complete Engineer

Everything was fine. That was the problem.

The project was stable. The team was humming along. The client was happy. My manager had no complaints. On paper, I was doing well.

But somewhere around year eight or nine, I started noticing this quiet unease that would show up every Sunday evening. Not stress. Not burnout. Something worse. Flatness. Like I was going through the motions of a career without actually going anywhere.

I had no name for it back then. I just knew that I was not learning anything new. The codebase was familiar. The problems were familiar. Even the meetings felt like reruns.

And the uncomfortable truth I kept avoiding was this: I had stopped growing without realising it.

The Thought That Changed Everything

I considered switching jobs. Most people do at that point.

But then a thought stopped me. What if the next project is just as stable? What if the next company has the same kind of work? There was no guarantee that a new job would bring real learning. And that realisation hit harder than I expected.

Why was I waiting for a company or a project to decide when I got to grow?

That question sat with me for a few days. And then, almost without a plan, I started thinking about building something of my own.

Not because someone told me to. Not because I read an article about side projects. Just because it was the only option I had not tried yet.

What I Actually Built

OTT platforms were everywhere at the time. Netflix, Hotstar, Prime Video. Everyone was jumping between apps trying to figure out what to watch.

So I decided to build an aggregator. A single web application where you could browse content across all three platforms, filter by genre, release date, OTT provider, and actually find something to watch without losing your mind.

Simple idea. Or so I thought.

The first problem I hit was the front end. I was a backend person. Always had been. I could work with existing HTML but building a new UI from scratch, with real CSS and styling, was a different world entirely. I spent days just thinking about where to even start.

Eventually I tracked down a former junior colleague who did front-end work. We struck a deal. He would build me three pages. Login, Main, and About. I paid him eight thousand rupees for it.

Eight thousand rupees for three HTML pages might sound like a lot. Looking back, it was one of the best things I spent money on. Not because of the HTML. Because of what paying for it forced me to do next.

What Nobody Tells You About Pet Projects

When those HTML files landed in my inbox, something shifted.

I had skin in the game now. I had paid real money. And suddenly I could not stop thinking about the application. During meetings at work. During lunch. On the commute home. I was mentally building it all day.

I would get home and just dive straight into it. Not because I had to. Because I genuinely could not wait.

Here is the thing I did not anticipate. I thought I was building an application. What I was actually doing was learning at a pace and depth that my job had never given me.

Think about what that one pet project required me to figure out:

What kind of application to build. How to think through product design without a product manager handing me requirements. How to find and evaluate front-end designs. How to work with a freelancer, brief them, and review their output. How to integrate a proper database. How to pick a cloud hosting provider. How to actually deploy an application live. How to purchase and configure a custom domain. How to set up SSL. How to track user activity. How to find and set up analytics tools.

None of that was on my plan when I started. I just wanted to build an app.

But that is exactly how pet projects work. You start with one thing and you end up learning ten. Not because someone designed a curriculum for you. But because the project itself keeps pulling you forward.

The Anxiety Disappeared

By the time I got the application running live on a real domain, something had changed in me.

That Sunday evening flatness was gone. The unease had quietly packed up and left.

I was not a different engineer technically. I had not learned a new framework or earned a certification. But I had built something end to end, alone, with no one telling me what to do or how to do it. And that changes you in ways that are hard to put into words.

You start seeing your job differently. Problems at work start feeling smaller because you have already solved bigger ones on your own. You become more resourceful. More confident in figuring things out without waiting for permission or guidance.

None of that came from my job. My job was never going to give me that. Not because my employer was bad. But because that is just not what jobs do.

What I Wish Someone Had Told Me

Growth in tech does not come from waiting. It never did.

Companies give you projects. Projects give you tasks. Tasks give you repetition. And repetition, after a point, stops being learning and starts being maintenance.

The engineers I have watched grow the fastest were almost always building something on the side. Not because they were told to. Not because it was career advice they read somewhere. Because they were curious about something and they went and built it.

That curiosity, and the accountability that comes from spending your own time and sometimes your own money on something, creates a kind of learning that no job can replicate.

I found that out by accident.

If you are reading this and your work feels comfortable in a way that no longer feels good, that feeling is not a sign that something is wrong with you. It is a signal worth paying attention to.

You do not need the right project to land in your lap. You can go build one.

Now Go Build Something

I mean that seriously. Not as a closing line. As an actual instruction.

It does not have to be impressive. My OTT aggregator was not used by anyone. Not a single real user. It was not a startup. It never made money. Nobody clapped for it. But it changed how I thought, how I worked, and how I showed up. That is not nothing. That is actually everything.

The idea does not have to be original. It does not have to solve a big problem. It does not have to be something you would put on your CV or talk about in an interview. It just has to be yours.

Start small. Embarrassingly small if that is what it takes to start. A tiny tool that solves something annoying in your own life. A script that automates something you do manually every week. A simple app around something you find genuinely interesting. The size of the idea does not matter at all. What matters is that you own every decision in it.

Because here is what will happen. You will hit a problem you have never hit before. And there will be no one to ask. No senior. No lead. No escalation path. Just you, a blank browser tab, and the problem. And you will figure it out. And the next time you hit something unfamiliar at work, you will feel a little less rattled by it. Because you already know you can figure things out on your own.

That is what a pet project really gives you. Not the code. Not the deployment. Not the domain. The quiet, unshakeable knowledge that you can build something from nothing.

Do not wait for the right idea. Do not wait until you have more time. Do not wait for someone to suggest it or approve it or tell you it is worth doing.

The journey will teach you more than you expect. It always does.

Pick something. Anything. And go build it.