Back-End Beginnings: From Hesitation to Enjoyment

After finishing the front-end section of the Codecademy Full-Stack Engineer Career Path, I went into the back-end portion with a bit of hesitation.

I’ve always felt more comfortable on the front-end — design, layout, and building user-facing experiences felt natural. Back-end development, on the other hand, felt more abstract. Less visual. More “under the hood”.

But a few weeks in, that assumption is already starting to change.

From Concepts to Something That Actually Works

So far, I’ve worked through the fundamentals of back-end development — Node.js, modular development, and building APIs with Express.

Projects like Message Mixer, Find Your Hat, and the Quote API have been small, but important. They’ve taken concepts that felt theoretical and turned them into something tangible.

There’s something satisfying about building an API endpoint and seeing it return data exactly as expected. It’s simple, but it works — and that’s the point.

Why I’m Enjoying It More Than Expected

One thing that’s stood out straight away is how logical back-end development feels.

CRUD operations — GET, POST, PUT, DELETE — are straightforward in principle, but they underpin almost everything. Once you understand that pattern, a lot of things start to click.

Express in particular has been a highlight. Compared to some of the front-end tooling, it feels lightweight and direct. Define a route, handle a request, send a response. No unnecessary complexity.

It also feels good to be back working in the terminal — running servers, installing packages, structuring projects. It feels closer to how I imagined “real” development before I started learning.

The Part I’m Still Figuring Out

The biggest challenge, once again, is logic.

Knowing what I want something to do is one thing. Translating that into clean, working code is another.

I still find myself pausing on relatively simple problems — working out what should happen step by step inside a function, or how data should flow through an application.

This isn’t new. It was the same on the front-end. But repetition is starting to make a difference. Rebuilding small projects, revisiting concepts, and making incremental improvements is slowly closing that gap.

On Using Help (and Not Feeling Like It’s Cheating)

One mindset shift I’m working through is around using external help.

Stack Overflow, documentation, Google, ChatGPT — they’re all part of my workflow at the moment. And sometimes that still feels like I’m taking shortcuts.

But realistically, this is how development works. The skill isn’t memorising everything — it’s understanding problems, finding solutions, and knowing how to apply them properly.

As long as I’m learning from what I use, it’s progress.

Where This Fits in the Bigger Picture

The biggest realisation so far is how the back-end supports everything the user sees on the front-end.

The UI is just the surface. The back-end is what actually makes an application function — handling data, managing requests, and connecting everything together.

Understanding that relationship is starting to make the idea of “full-stack” feel a lot more real.

Next up is middleware, followed by databases, authentication, and eventually a full e-commerce API project. There’s still a long way to go, but this part of the journey is already more enjoyable than I expected.