Command Palette
GitHubSearch for a command to run...
What building production features on the MERN stack at PRISM taught me that university courses didn't.
A few months into my internship as an Associate Software Developer at PRISM (formerly OYO), a handful of lessons kept repeating in different forms. None of them are groundbreaking, but they weren't obvious to me from coursework alone.
A university assignment is done when it produces the right output for the given test cases. Production code has to also handle the input nobody thought to test, degrade gracefully when a downstream service is slow, and be readable by someone who didn't write it. That last one is the hardest habit to build.
Most of the hard problems I hit weren't about React or Node.js themselves — they were about data modeling, caching invalidation, and making sure a MongoDB query didn't do a full collection scan under load. The framework choice mattered far less than getting the fundamentals right underneath it.
Getting a PR reviewed by someone with more context taught me more per hour than most solo debugging sessions. Learning to review other people's code well — flagging the right things, not nitpicking style — turned out to be just as valuable as writing my own.
The instinct from academic work is to keep polishing until it feels "finished." In a real product, a working, well-tested version shipped today beats a theoretically cleaner version shipped next sprint. Iteration is the actual mechanism for getting to quality, not a consolation prize.