/explore
|
You are here 
|
lukasrotermund.de | ||
| | | | |
www.alexedwards.net
|
|
| | | | | ||
| | | | |
www.integralist.co.uk
Interfaces in Go Name Your Interface Arguments Keep Interfaces Small Accept Interfaces, Return Concrete Types Don't Return Concrete Types Use existing interfaces Don't Force Interfaces Embedding Interfaces Upgrading Interfaces Standard Library Interfaces Tight Coupling Dependency Injection Refactoring Considerations Testing More flexible solutions? Conclusion This post is going to explain the importance of interfaces, and the concept of programming to abstractions (using the Go programming language), by ... |
|
| | | | | ||
| | | | |
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. |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
