eugenezalens

1,000 subscribers, just 2 weeks in.

Honestly, thank you.

I started this channel from zero with one simple idea: to talk about frontend architecture, component design, and production-grade systems in a way that feels deep, practical, and actually useful.

Seeing this kind of response so early means a lot.

Thank you for watching, subscribing, commenting, and sharing your thoughts. It really gives me energy to keep building this further.

Special thanks to my Polish audience 🇵🇱

The next video is already in progress and will be released this Thursday.

This time, we’ll talk about component organization: where components should live, how to avoid turning `components/` into a dumping ground, and how to structure UI in a way that actually scales.

More is coming.

1 month ago | [YT] | 6

eugenezalens

Hello everyone.

Honestly, I did not expect the audience to start growing this quickly — especially considering that the first video was published just a couple of weeks ago.

Thank you for the trust, the attention, and the interest in what I’m building here.

I wanna share a bit about the next couple of videos.

This Thursday, I’m releasing a new episode focused on data-access in frontend applications. Almost every project has some layer that handles requests. It can be TanStack, RTK, GraphQL, or even plain native fetch — that part is not the most important one right now.

In the next video, I wanna show one way to build an extensible API layer so that you don’t keep duplicating logic, you keep DRY in mind, and at the same time you don’t end up with a system that becomes unnecessarily complex — the kind where every small change makes you want to run regression testing across half the project. And yes, of course, SOLID matters here too.

But the most important part is this: I want to show the actual architectural approach I personally like to use in my own projects — the one that has proven itself really well in practice.

I think this will be especially interesting for people whose projects receive data directly through SSR, ISR, native client-side fetch, or a mixed approach. I’ll also touch on mutations. And of course, I’ll talk a little about cache as well.

That said, cache itself will get a separate video. Preparing that one properly is much harder, because to demonstrate it the right way, I need a real backend. Otherwise, I lose the core idea behind this channel — the quality of the final content. I do not want to make an example just for the sake of having an example. I want to make a video where you can actually see this architecture working inside a real project. A small one, yes — but nothing stops you from extending it further 😊

That is really the whole point of these videos.

And once I finish the current scope — Cache, Routes, Independence — I want to move into a series on microfrontends. It is a popular topic, a very visible one, but definitely not a simple one. That series will require a lot of preparation, because I want to keep the quality bar exactly where it should be.

Thank you again.

Wishing you clean systems and good projects.
See you in the next video.

1 month ago | [YT] | 3