Explore >> Select a destination
|
You are here 
|
markphelps.me | ||
| | | | |
mfbmina.dev
|
|
| | | | | 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. The other big role in daily work is to write tests. Tests ensure (or should guarantee :D) that all the code written by us works on how it is expected and, therefore, it will not happen any surprises when the feature is running at production environment. | |
| | | | |
benhoyt.com
|
|
| | | | | My re-implementation of the code from the official Go tutorial 'Developing a RESTful API with Go and Gin', using only the standard library, adding tests, and fixing issues. | |
| | | | |
atilaoncode.blog
|
|
| | | | | D has built-in unit tests, and unittest is even a keyword. This has been fantastically successful for the language, since there is no need to use an external framework to write tests, it comes with the compiler. Just as importantly, a unittest after a function can be used as documentation, with the test(s) showing up... | |
| | | | |
andreasimonecosta.dev
|
|
| | | Let's try to clarify, once and for all, the true essence of type parameters. | ||
