Why I’m learning the MERN stack as a frontend developer

I have spent most of my career on the frontend: converting designs into HTML and CSS, building WordPress themes, and more recently working with Next.js and TypeScript. I am now learning the rest of the MERN stack, MongoDB, Express and Node.js. This post is about why.

Understanding the other side of the API

For years I have worked closely with backend developers, integrating frontend components with server-side logic. Knowing how APIs are built makes me better at consuming them. I want to understand routes, validation, error handling and authentication from the inside.

React and Next.js already point that way

The frontend part of MERN is React, which I already use through Next.js. Learning Node.js and Express means the whole application is in one language, from the database query to the button the user clicks. If you are coming from WordPress too, I wrote about what to know before starting with Next.js.

What I am focusing on

• Building REST APIs with Express: routing, middleware and error handling
• Modelling data in MongoDB, and when a document database fits better than a relational one
• Authentication and keeping secrets out of the codebase
• Connecting a React front end to my own API

Learning in public

I plan to write about what I build and what I get wrong along the way. Writing things down is how I check that I really understand them.

Not leaving the frontend behind

Frontend quality, accessibility and performance are still where I do my best work. Full-stack knowledge makes that work stronger. It means fewer assumptions about how the data arrives, and better conversations with the people building the backend.