Following Data Through Next.js, Node, Express, and MongoDB

My internship at Lectrium introduced me to a JavaScript and TypeScript stack that extended beyond individual React components. Working around Next.js, Node.js, Express, and MongoDB helped me understand how an interface is connected to the services and data behind it.

On the frontend, Next.js provided the structure around React pages and components. On the backend, Express organized how requests entered the application, while MongoDB represented data in a form that mapped naturally to JavaScript objects. Seeing these layers together made abstract full-stack concepts much more concrete.

I learned to follow data through the entire request: where it originated, how it was transformed, what the UI expected, and how an error should appear to the user. TypeScript helped surface mismatched assumptions during development, while runtime checks remained important at the API boundary.

That experience gave me a foundation for later full-stack work. Technologies change, but the central questions remain useful: Which layer owns this responsibility? What assumptions cross the boundary? And how can the system make failures understandable rather than surprising?