Explore >> Select a destination
|
You are here 
|
antonz.org | ||
| | | | |
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. | |
| | | | |
rosshemsley.co.uk
|
|
| | | | | When it comes to reviewing code that does any kind of file IO, there are a number of patterns that I find myself discouraging quite often. Interestingly, I have found that these patterns are rarely considered in discussions around code review and clean code. In this post, I will explore some of these patterns in more depth, and discuss why I believe its worth taking the time to do things slightly differently in many cases. | |
| | | | |
lukesingham.com
|
|
| | | | | These are my summary notes of 'A Tour of Go' - which is meant for people who are familiar with programming to have a quick tour | |
| | | | |
www.philosophicalhacker.com
|
|
| | | |||
