TL;DR -> Don’t have time 🙂? Check out this repository where I present an easy way to include feature toggle in your API. Enjoy!
In many companies, during long migrations from monolith-based software to microservices, the idea of continuous deployments feels something out of reach.
TL;DR -> Checkout this repository to see how the bad-request and unprocessable-entity responses are managed at different levels of the asp.net core application.
One of the most important aspects of a great API is the way in which it responds to its clients. How it returns the expected results and how errors are reported with proper (and unique) codes and descriptions are a couple of topics to care about while you are developing an API.
During the development of a REST API, there are mainly two types of errors that our clients care about:
Tell your clients what they are doing wrong :)
No time to lose? Check out this repository😊!
Straight to the point! 😄
Let’s imaging we need to develop and REST-API. For the sake of the example, we will build the API using Asp.Net core with C#.
This API will have one endpoint that will:
Basically, a curl request to this endpoint would look something like this:
curl --location --request GET 'https://localhost:5001/fv?query-prop-name=10' \
Why Git-Flow might not be the best idea for you
Every time a new team is assembled, we need to think about how teammates are going to work together. Share code, testing stages, deployment gates, … A bunch of technical words start appearing during (long) conversations where everybody is eager to provide his opinion.
When a project is about to start there is a lot of uncertainty and is difficult sometimes to know the requirements. Also, the team doesn’t know how the best way to develop is going to be since the number of people involved might change very soon…
A smooth introduction to versioning and release notes automation using Git.
TL; DR -> Don’t have time to read the article 🙂 ? Check out this repository and you will find a completely functional node script that you can use to version and generate release notes automatically after each merge on your main branch. The script is a simplification of the one we use in my company for continuous integration and it is meant to work on bitbucket.
Still here 😄? Okay, let’s have a look at this script 😁❗
Since the start of 2020, I’ve been involved in a…
TL;DR -> If you are in a hurry, take a look at those two repositories. You’ll find a detailed comparison between the same service tested using two different strategies.
If you have five minutes, let’s take a look in detail 😃❗
Since almost the start of my career, I’ve been involved in the development of REST APIs using Asp.Net core. It is a great framework that uses c# and provides many awesome tools, I encourage you to consider it if you are thinking to develop some APIs.
TL;DR -> For those of you that are always in a hurry 🙂, check out this repository. You can find an example of a .gitconfig file that allows me to automate all the tasks that involve Git.
Do you have 5 minutes? If so, let’s do this together 🦾!
As a developer, I find myself using Git almost every day (dozens of times a day in fact) to manage the code my team manages in several repositories we own.
If you read my previous articles, you’ll realize I’m quite a fan of Git but, most importantly, I’m obsessed with automation…
As a software developer, I spend most of my time dealing with GIT. This magic tool that, if you know how to use it, can make your life so easy but, if you treat it badly, can easily backfire.
In this article, I’ll try to show and explain my most used GIT commands at work. How I use them and why. I’ll try to list them following a typical development flow but a little GIT knowledge from the reader might be required 😉.
Have you ever needed to press F5 on a website to refresh the content? git…
Not long ago, I was asked by one of my product owners (PO) to resolve a bug one of our clients encountered. The content of the bug is not relevant but the PO asked me a series of questions (all of them quite reasonable 🙂):
Well, at that moment, I was quite new to the company, and my experience in the code-base was minimal. Also…
Proud teacher-volunteer at Migracode and Cloud-engineer at Ohpen where I keep pushing my AWS+Serverless knowledge every day.