mfbmina.dev

In my opinion, Go provides excellent support for concurrent work, not only due to goroutines but also because of the language’s ecosystem.

Imagine the following problem: you need to process hundreds of records and generate a single output.

In a previous post I showed some ways to improve tests by creating API mocks that we call.

As the software we work on grows, the code tends to undergo various changes and refactorings.

At my Circuit Breaker post, I mentioned that nowadays it is common that the application has to communicate with other ones, and with that, traffic control strategies become essential.

Atualizações importantes Hey guys, editing the post to say that after talking to some people, I noticed that I whole misunderstood how Go dependencies work, and I was expecting some feature that already kind of exists, since just what is used from the code

One of my favorite features in Go is the possibility of writing benchmark tests.

After reading the book The Goal, I went after the next reading, and I was recommended to read The Mythical Man-Month, from Fred Brooks.

Nowadays, a huge part of a developer’s work consists in calling APIs, sometimes to integrate with a team within the company, sometimes to build an integration with a supplier.

At the developing world, it is necessary to know how the application that you’re working on is behaving, and the most known way of doing that is by metrics.