Great overview of many common Go mistakes. I've learned quite a lot, especially towards the later chapters. The examples sometimes seemed a little too 'contrived,' I guess that's just the side effect of trying to keep code extracts as short and concise as possible. I would've wished for some more real-world examples though.
User Profile
I can resist everything except temptation.
I read pretty much anything with a halfway interesting title, although mostly SF and technical books about programming.
Pronouns: any
This link opens in a pop-up window
Attaboy's books
2025 Reading Goal
33% complete! Attaboy has read 4 of 12 books.
User Activity
RSS feed Back
Attaboy started reading V for Vendetta by Alan Moore
Attaboy finished reading The Crow by James O'Barr
Attaboy started reading The Crow by James O'Barr

Attaboy quoted Fifty Great Short Stories by Milton Crane
In this moment she felt that she had been robbed of an enormous number of valuable things, whether material or intangible: things lost or broken by her own fault, things she had forgotten and left in houses when she moved: books borrowed from her and not returned, journeys she had planned and had not made, words she had waited to hear spoken to her and had not heard, and the words she had meant to answer with; bitter alternatives and intolerable substitutes worse than nothing, and yet inescapable: the long patient suffering of dying friendships and the dark inexplicable death of love -- all that she had had, and all that she had missed, were lost together, and were twice lost in this landslide of remembered losses.
— Fifty Great Short Stories by Milton Crane, Milton Crane (Page 227 - 228)
Attaboy started reading Rust for Rustaceans by Jon Gjengset

Rust for Rustaceans by Jon Gjengset
For developers who’ve mastered the basics, this book is the next step on your way to professional-level programming in Rust. …
Attaboy reviewed 100 Go Mistakes by Teiva Harsanyi
Attaboy finished reading 100 Go Mistakes by Teiva Harsanyi
Attaboy quoted 100 Go Mistakes by Teiva Harsanyi
Let's not try to solve a problem abstractly but solve what has to be solved now.
— 100 Go Mistakes by Teiva Harsanyi (Page 24)
Attaboy quoted 100 Go Mistakes by Teiva Harsanyi
As we discussed, interfaces are made to create abstractions. And the main caveat when programming meets abstractions is remembering that abstractions should be discovered, not created. What does this mean? It means we shouldn't start creating abstractions in our code if there is no immediate reason to do so. We shouldn't design with interfaces but wait for a concrete need. Said differently, we should create an interface when we need it, not when we foresee that we could need it.
— 100 Go Mistakes by Teiva Harsanyi (Page 24)
Attaboy started reading 100 Go Mistakes by Teiva Harsanyi
Attaboy started reading What If? by Randall Munroe

What If? by Randall Munroe
Randall Munroe left NASA in 2005 to start up his hugely popular site XKCD 'a web comic of romance, sarcasm, …
Attaboy quoted Fall; or, Dodge in Hell by Neal Stephenson
[...] who had apparently had what Richard had had in the way of an infatuation with these books.
— Fall; or, Dodge in Hell by Neal Stephenson (Page 12)
What?
Attaboy quoted Fall; or, Dodge in Hell by Neal Stephenson
He wondered whether the designers of the phone had performed clinical studies on snoozers in order to decide on the nine-minute interval. Why not eight minutes, or ten? The makers of the phone were famously particular about design. This had to have been data-driven. It was no coincidence that Dodge was being afforded just enough time to lose the thread of consciousness before the alarm went off again. If the interval had been much shorter, he would not have had time to drift off and so this feature could not have truly been called a snooze alarm. Much longer, and the snooze would have deepened into true sleep.
— Fall; or, Dodge in Hell by Neal Stephenson (Page 6)
It's so much better when people with a good understanding of current technology write SF.