Open source is one of the most fascinating things I’ve ever encountered in our industry. It is a movement that essentially groups people together to work on a product because they want to. They usually do it for free, especially during the first stages of the project, and then — get this — they maintain it so that others can use it. Also for free.

I tend to think that if more industries were to adopt open source as we do in software development, things would be a lot easier. Then again, that’s not why we’re here. …

The dream of being your own boss is one that almost everyone goes through at some point during their career. For some strange reason, we tend to believe we can do away with concepts such as “boss,” “9 to 5,” or “team meetings” and just sit down, put our head down, and work on what we love. Like that would solve all our problems.

In some cases, this notion becomes more than just a dream; some people actually succeed at freelance. More often than not, it either remains a dream or quickly becomes a nightmare. …

So you have your PoC ready and working, you’ve successfully proved to the business that your idea works. “Fantastic!” they say, “let’s deploy it to production next week” they also say, and you suddenly realized they didn’t really understand a single thing you said.

Granted, this doesn’t happen in every situation, sometimes we’re able to correctly communicate the need to refactor and keep working before we can actually deploy an idea into production. …

Which is better, PHP or Node.js? Or perhaps this one: Which is easier, frontend development or backend development?

As developers, we tend to ask these types of questions, trying to find an answer that doesn’t really exist. Which one is better, object-oriented programming or functional programming? That’s like asking which one is better, being able to see or being able to hear.

Let me solve the mystery quickly and simply: They’re both equally important, and it’s only you who can decide, for your particular context and set of needs, which one is actually better. Will your answer apply to me…

How many times have we been pushed into working on a feature because, and I quote, “It’s now or never. If we don’t change this now, it’ll be too expensive to change in the future”?

This is the premise of this article. Whether it’s because of a deadline, a lack of knowledge, or maybe even faulty requirements, sometimes we tend to cut some corners when writing our code, and that leads to future problems and the classic //TO-DO: Fix me comment that never gets resolved.

If we’re lucky enough, we might be able to tackle some of those to-dos in…

Redis is one of the most powerful and versatile pieces of technology I’ve come across. Sadly, most people only know it because it makes for a good caching solution.

We need to fix that.

In particular, I want to show you that you can create a reactive architecture having Redis as the main component. This is a huge plus, especially if you already have it as part of your infrastructure due to other requirements (i.e the good ol’cache).

What you use with Redis to interact with the features I’ll be describing here is up to you, honestly at this point…

Design patterns are there to keep us from reinventing the wheel, algorithmically speaking, that is.

They provide us with a template of how to best structure our code and how each component should communicate with each other.

And the command pattern is no exception, giving us a way to encapsulate part of our logic while decoupling from the rest of the project. This is by far, one of my favorite design patterns and this is why I wanted to cover it here.

What is the Command Pattern?

Long story short, the command pattern is a behavioral pattern (meaning, it takes care of solving how objects…

Github has been shaping the way software developers work for a while already, focused mainly on the way they do version control of their code, and how they share their work with others.

Tools to simplify the way we work together, the way we review each other’s work, they’ve made the concept of code repository evolve up to a point where they’ve become a standard in our industry.

Recently Github announced their latest piece of innovation to help move the industry forward: Copilot a code generation tool that learned from all of our publicly available code.

The question now is…