What building a real product taught me about ownership

Building Tresra has been one of the most challenging and educational projects I’ve worked on so far.

I’m leading the overall project and team while handling the backend and mobile application, alongside my backend development partner @riya_jangid1 .

One thing this experience made very clear to me is that building a real product is very different from simply building features.

When you're responsible for a product, you start thinking about things that don't always matter when you're working on isolated features: architecture, security, scalability, deployment, maintainability, environments, infrastructure, and what happens when something inevitably goes wrong.

It also pushed me to step outside my existing comfort zone. During the project, I worked with technologies and infrastructure that were relatively new to me, including Cloudflare, Supabase, Docker, Spring Boot environment management, deployment infrastructure, and more.

But the biggest lesson wasn't any particular technology.

It was ownership.

You start realizing that a technical decision isn't just about whether something works today. You have to think about how it will affect the team, the product, future development, and the people who will eventually use it.

That shift in thinking has probably been the most valuable part of building Tresra for me. It has pushed me to grow not only as a developer, but also as an engineer and technical lead.

I'm curious to hear from other makers here:

What was the project or experience that changed the way you think about software engineering?

Was it moving from side projects to production, taking ownership of a system, leading a team, dealing with real users, or something completely different?