Building a Redux App Without the API I Was Meant to Use

When I started this project, the goal was clear: build a Reddit client application using React and Redux as part of the Codecademy Full-Stack Engineer Career Path.

The brief assumed access to the Reddit API. In reality, by the time I reached this project, the required endpoints were no longer publicly accessible without authentication or paid access.

At that point, I had two choices - abandon the project, or adapt it in a way that still demonstrated the intended skills. I chose the second option.

Adapting the Brief Without Losing the Point

Rather than focusing on API wiring, I reframed the problem around what the project was actually trying to teach:

Global state management with Redux, async request lifecycles, UI state handling (loading, error, empty states), component architecture, testing, and deployment.

The application was restructured to simulate a Reddit-style experience, with posts and comments managed through Redux slices and async thunks that mirror real API behaviour.

This allowed me to focus on state design and data flow - which turned out to be the most challenging and valuable part of the project.

The Jump From Tutorial to Application Is Real

This was the first project where the gap between “following along” and “building something” really hit.

Redux, in particular, forced me to think carefully about where state should live, how slices interact, how UI reacts to async changes, and how to test behaviour rather than implementation.

I struggled — a lot. But that struggle exposed gaps in my understanding that I wouldn’t have noticed otherwise.

Testing and Deployment Changed Everything

Writing unit tests and end-to-end tests made weaknesses in my assumptions obvious very quickly.

Deployment was another wake-up call: ESLint warnings failing CI, differences between local and production environments, and the need to pay attention to performance and accessibility.

These are things tutorials rarely emphasise, but they matter in real projects.

What This Project Represents

This app isn’t impressive because of what it looks like. It’s valuable because of what it represents.

Adapting to real-world constraints, finishing a project when the path isn’t straightforward, learning how tooling, testing, and deployment fit together — and shipping something that works.

That, to me, is what learning to be a developer actually looks like.