From 66b52982544237301271a5aac45d96972ea90f92 Mon Sep 17 00:00:00 2001 From: Teiva Harsanyi Date: Wed, 14 Sep 2022 13:28:45 +0200 Subject: [PATCH] Adding link to concurrency faster post --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e67354a..f02bdfc 100644 --- a/README.md +++ b/README.md @@ -264,7 +264,7 @@ In many cases, you shouldn’t ignore an error returned by a `defer` function. E Understanding the fundamental differences between concurrency and parallelism is a cornerstone of the Go developer’s knowledge. Concurrency is about structure, whereas parallelism is about execution. -#### Thinking concurrency is always faster (#56) +#### [Thinking concurrency is always faster](https://teivah.medium.com/concurrency-isnt-always-faster-in-go-de325168907c) (#56) To be a proficient developer, you must acknowledge that concurrency isn’t always faster. Solutions involving parallelization of minimal workloads may not necessarily be faster than a sequential implementation. Benchmarking sequential versus concurrent solutions should be the way to validate assumptions.