"I have two news for you, bad and worse," said the mechanic. "The battery is dead and I won't get a new one until Monday. Forget about your annual inspection today," he continued. "But..." you started. "There is no but." he cut short. No setup, no testing. Just like in your Go program.| Jakub Jarosz
We focus on fundamental parts of the cmp package: checking equality and calculating diffs. With a small change, you increase test efficiency more than 7x. Yes, over 700% faster. Why work harder, not smarter?| Codes on Jakub Jarosz
In Go, we build packages - fundamental Lego-like blocks that we assemble in modules and use to build applications. That's why it's crucial we start designing packages by modelling their public APIs. Let's roll up our sleeves, sharpen the scalpel and start the second code surgery. This time, we focus on tests.| Jakub Jarosz
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