5 posts tagged with "backend"

There's a type of bug that doesn't break the build, doesn't show up in the logs, doesn't land in Sentry, but kills your product overnight: user A opening the application and seeing — out of nowhere — user B's data. Transaction, balance, tax ID, address, whatever. And the worst part: in almost every project where I saw this happen, the problem wasn't "a bug" in the code. It was the total absence of RLS in the database.

Today I want to talk about Row Level Security, which is literally the wall that separates one user's data from another's — within the same table.

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.

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.

One of the hardest things in a Node project is keeping libraries up to date. Anyone who works with package management using Node knows exactly what I am talking about. In production, a project can easily scale its libraries — and consequently the sub-dependencies that come along — making the task of keeping everything updated quite challenging.

Software Architecture​

Infrastructure for Credit](https://cdn-images-1.medium.com/max/2000/1*gAvcIkpA_3emvVIcLEq6tQ.png)

When we talk about Software Architecture it is common to reference the main aspects of the design of a software system. Architecture is something very important and has the power to make a project/company a success or a great failure, depending on how it was planned and executed.

In this article I will discuss Software Architecture, its importance, risks, and what impact it has on your product/service/business.