> By four days in of exploring Go I had mastered most of the language, had a working program and tests, and was adding features to taste. I felt this way too b

> By four days in of exploring Go I had mastered most of the language, had a working program and tests, and was adding features to taste. I felt this way too but then realized the advanced topics of Go really take time to get right. Writing correct concurrent code is non-trivial as you need to tailor your solution to the problem at hand. There is no one size fits all way to write concurrent code. In some cases a mutex makes sense whereas channels work better in others. Programmers must be diligent when using these tools as well because of deadlocks, data races, or go routine leaks. I think this is an area Rust excels in with its ownership model that eliminates these problems.