13 posts tagged with "frontend"

Anyone who has spent hours chasing an undefined in the middle of a bundle or a strange behavior only in production knows how an unresolved import chain can become a headache. One of the frequent culprits is the circular import: module A imports B, B imports C, and somewhere in the chain someone imports A again — closing a cycle.

It's wonderful — the build works, the project runs locally, but when you try to deploy, it breaks! \o/

I've seen this in small projects and in large ones; the only difference is the size of the problem you'll face. You can spot the headache with Madge and it's a lifesaver!

To lock up TypeScript, a circular import is a treat.

Many people ask me how to organize their studies in technology. There's no single path, but it's possible to think in learning levels that provide clarity and direction.

I've put together a list of items to make studying easier, going from the basics to advanced.

Many people still associate the term frontend only with the visual appearance of a website or application — colors, buttons, layouts.

That famous phrase "it's just a button." But they don't understand what's behind that simple button that triggers multiple actions in the user interface and, in most cases, in other systems via API, for example.

Front-end development is frequently misunderstood. Many people still limit its definition to the purely visual layer — "just put a button there" or "just need to change that color." This misconception underestimates the complexity and impact that architectural decisions have on modern web development.

And with the rise of Vibe Coding, this view can be amplified. Frontend is just HTML and Backend is a bunch of CRUDs.

Those who work with development know that's not how it works. A simple system built in 1 hour that scales? Good luck.

This is an article I've wanted to write for a long time but kept putting off... Today I woke up at 5am and, by some hidden force of nature, sat down in front of the PC to write something mysterious that came out of my head.

Without further ado, the goal here is to describe some Front-end architectures — a complex and strangely underaddressed topic.

In this article I'll cover an example of architecture and the traps of not following a well-defined pattern. What I bring is the software developer's perspective and things they should care about to mitigate future problems, for themselves and for the company.

Software architecture is about what matters to the business.

Career growth is a very important topic — and it can often be challenging to chart the right path or choose the ideal topics to study.

With that in mind, I'm sharing here some essential topics for those who want to enter or deepen their knowledge in Front-end development.

Application design is an extremely important topic in software development. I see many people with no idea how to create a good architecture, which can create major complications as the system evolves — new features, new demands, problems, delivery pressure, and many other factors that contribute to increasing application complexity.

Entire systems can be rebuilt simply because the team failed to create a good architecture, or at least an ideal starting point that allows the project to evolve and adapt. This can happen for various reasons: lack of knowledge and pressure to deliver (very common). The latter creates a trap by assuming that skipping precious software development steps in the name of speed and delivery won't affect quality and scale.

In this article I'll cover some problems that can arise from not following a well-defined standard. My goal is to bring the software developer's perspective and things they should care about to mitigate future problems — for themselves and for the company.