In software development, patterns help us solve common problems or situations by following a well-known set of approaches. Those approaches have been tested for a long time and have proven useful in some scenarios. Patterns also allow developers to speak the same language, and refer to some development techniques by the pattern name, instead of explaining their behavior.

Patterns are language agnostic, which means they are not bound to a programming language or a stack. However, some languages make easier the implementation of some of them than others.

There are lots of software development patterns, being the most famous the ones published by the Gang of Four. You have a summary of them here.

In this post, we are talking about how to implement the “strategy pattern” in a .NET Core API.

Read More

Mails are the norm in nowadays communication in companies. Long threads of emails with dozens of people included in the recipient lists fill out inboxes. Some of those emails require some sort of action on your part, while others are just either informative or, directly, irrelevant. However, every time you go back to your email client, you feel overwhelmed with all those emails waiting for you. In fact, even leaving your email client closed may not free your mind, as those to-process emails will remain in some part of your brain, yelling at you.

Read More

A peer review is both a functional and a code review performed between two or more people (from now on, the “reviewers”).

The developer who completes a user story (from now on, the “creator”) shows his work to other teammates to get feedback about it, before showing it to the final customer.

Read More