Wake up one thread, not the whole room
Why concurrency bugs need a different kind of debugging.
posts tagged #go
Two safe pieces of code can combine into an unsafe one
Combining two perfectly correct concurrent modules can still produce a deadlock.
The reader-writer lock I trusted has a hidden cost
RWMutex sounds like a free lunch. It isn't.
Not all your code deserves a clever lock
Most concurrency bugs come from optimizing code that never needed to be fast in the first place.
I benchmarked two ways to handle concurrency. One was 13x faster.
Channels feel cleaner. Mutexes are faster for reads.
Don't share memory to communicate. Communicate to share memory.
Go has a different answer to concurrency than most languages.
I crashed my server on purpose to understand why
What happens when two goroutines write to the same map at the same time.
My first week of Go: building a tiny TCP server
How I built a TCP server in Go from scratch and what actually made things click.