I learned engineering by building, not by grinding.

I'm Govind. I joined an early-stage startup as a 4th-year BTech intern and started shipping production code almost immediately. I came from a normal tier-3 college. I graduated with a gold medal, but I've never thought of that as my real achievement.

My actual growth started after I joined.

The path I didn't take

I'm not the developer who spent years grinding interview questions. When I joined, I had basic programming knowledge and some full-stack fundamentals, but almost no production experience.

The product wasn't mature. The company wasn't mature. The processes weren't mature. We were figuring things out while building — no perfect roadmap, no certainty about where the product would end up. We learned from users and evolved.

Learning during the AI era

I entered software during the rise of AI-assisted development. A lot of the early work involved tools like Gemini and Claude. But I never blindly accepted what they produced.

I worked under engineers with more than a decade of experience who reviewed everything carefully. They rejected my PRs. They asked me why. They made me defend my choices.

Many of my most valuable lessons came from things I first disagreed with — until months later a real need proved they mattered.

Ex: extracting strings into constants. Design consistency. Writing tests. Naming conventions. Feature gating. I learned the value of each one long after I'd argued against it.

What I actually learned

I learned software engineering by shipping, debugging, maintaining, and improving a real SaaS system. I learned from mentors. From mistakes. From customers. From testers. From production incidents. From building.

Good engineering optimises for the change you can't see coming, not just the task in front of you. That's the lesson under almost everything I write here.