Full Stack Development in Production: Lessons from Ninepages Techsolutions

Seventeen months building client work as a Full Stack Engineer at Ninepages Techsolutions in Agra taught me more about state management than any tutorial ever did — mostly by showing me how *not* to use it.

Redux is easy to reach for and easy to overuse. A lot of what I actually learned there was where state should live: what belongs in a global store, what belongs in local component state, and what should never have been state at all and could just be derived on render.

The other constant was MongoDB schema design under real client requirements that changed mid-project. Flexible schemas are a gift until three different features assume three different shapes for the same document — after that, you start writing validation layers whether the client's spec asked for them or not.

Working on-site with a small team meant shipping features end-to-end — frontend, API, and database — instead of owning one layer. That full-stack ownership is probably the single habit that's carried over most directly into everything I've built since.