A few weeks ago, I read an article called “Good Code vs Bad Code in Golang” where the author guides us step-by-step through the refactoring of an actual business use case. The article focuses on turning “bad code” into “good code”: more idiomatic, more legible, leveraging the specifics of the go language. But it also insists on performance being an important aspect of the project. This triggered m
![Go code refactoring : the 23x performance hunt](https://cdn-ak-scissors.b.st-hatena.com/image/square/44ebfcee67350b8d19ecc5ae80cc8d6798c3e512/height=288;version=1;width=512/https%3A%2F%2Fmiro.medium.com%2Fv2%2Fda%3Atrue%2Fresize%3Afit%3A400%2F1%2ABshU9W-WAWyJKyLWASEA_Q.gif)