This week we do small refactoring to illustrate how we can improve code readability and reduce cognitive load.| Jakub Jarosz
For us Go developers, writing less code means fewer opportunities to make mistakes. But how about achieving more by doing less? That sounds appealing. Isn’t it? And how about spending less time writing code to force the compiler not to optimise the benchmarking functions?| Jakub Jarosz
How do you know if what you are building is the right thing? How do you know if the product you just put into customers' hands doesn't harm them? Don't put them into hospital or worse, kill them?| Jakub Jarosz
How should I organize my Go code? What directories to create? How many nesed levels? Where to put what files? How about tests and test data? Shall I follow this and that template? Could we automate project structure generation?| Jakub Jarosz