From Front-End Comfort to Back-End Confidence

Back in March, I wrote about starting the back-end section of the Codecademy Full-Stack Engineer Career Path with a fair amount of hesitation.

At the time, I was coming off the front-end modules, where I felt much more comfortable. Building interfaces, styling pages, and creating things users could actually see felt natural. The back end felt more abstract and, if I'm honest, a little intimidating.

Fast forward a few months and I'm now roughly 50% of the way through the back-end section of the course.

It's probably a good time to take stock of what's surprised me, what I've enjoyed, and how my perspective has changed.

SQL Wasn't Supposed to Be This Enjoyable

If you'd asked me before starting this section what I'd enjoy most, databases wouldn't even have made the shortlist.

But SQL has quietly become one of my favourite things I've learned so far.

Working with PostgreSQL through Postbird has been surprisingly satisfying. Creating tables, querying records, updating data, and seeing everything come together feels incredibly logical.

One of the projects I completed recently involved building and managing a films database. It wasn't the most complex project in the world, but it was one of those moments where concepts stopped feeling like exercises and started feeling like practical skills.

Compared to JavaScript, SQL feels refreshingly direct. Ask a question, get an answer. Structure your query properly, and the database gives you exactly what you asked for.

There's something very satisfying about that.

Testing Started Clicking

Another standout module has been back-end feature testing.

Having already worked through Test-Driven Development on the front end, this felt familiar in all the right ways.

More importantly, it reinforced something I've started noticing throughout the Full-Stack path: concepts rarely exist in isolation.

The more I progress, the more topics begin connecting together. Ideas that felt separate a few months ago suddenly make much more sense when viewed as part of a larger application.

Testing was a great example of that.

Boss Machine and Building Real Structure

The Boss Machine project was another highlight.

Working with Express.js, routes, middleware, and application structure made the back end feel much more tangible than some of the earlier modules.

Authentication and route logic have probably been the closest thing to a challenge so far. Not necessarily because the concepts are difficult, but because understanding where everything belongs takes time.

As applications grow, there's a lot more to think about than simply writing code that works.

Organisation, structure, and maintainability start becoming just as important.

Full-Stack Is Starting to Make Sense

The biggest takeaway from the last few months is that I've stopped seeing the front end and back end as separate disciplines.

They're obviously different, but I'm starting to appreciate how closely connected they really are.

The front end is what users interact with. The back end is what makes those interactions meaningful.

Understanding both sides of that relationship is what makes full-stack development so appealing to me.

If I had to choose today, I'd probably still lean slightly towards front-end development. But much less than I would have a few months ago.

The further I get into the back-end path, the more I'm enjoying it.

There's still plenty left to learn, and I'm fully expecting the difficulty curve to continue climbing. But reaching the halfway point has definitely reinforced that this was the right path to take.