1 Go: Simple to Learn but Hard to Master

 

This chapter covers

  • What makes Go an efficient, scalable, and productive language
  • Exploring why Go is simple to learn but hard to master
  • Presenting the common types of mistakes made by developers

Making mistakes is part of everyone’s life. As quoted by Albert Einstein:

Anyone who has never made a mistake has never tried anything new.

-- Albert Einstein

What matters, in the end, is not the number of mistakes we make but our capacity to learn from them. This assertion also applies to programming. The seniority we acquire in a language isn’t a magic process; it involves making many mistakes and learning from them.

The purpose of this book is centered around this idea. It will aim to help you be a proficient Go developer by discussing 100 common mistakes in many areas of the language.

In this chapter, we will remind us why Go became mainstream over the past years, understand why despite being considered as simple, it doesn’t make it an easy language, and finally, present what you will get from this book.

1.1 Go outline

If you read this book, it’s likely that you’re already convinced about Go. Therefore, let’s be brief to remind us what makes Go a powerful language.

1.2 Simple doesn’t mean easy

 

1.3 100 Go mistakes

 
 
 
 

1.3.1 Bugs

 
 
 

1.3.2 Needless complexity

 
 
 
 

1.3.3 Weaker readability

 
 

1.3.4 Unidiomatic organization

 

1.3.5 Lack of API convenience

 

1.3.6 Under-optimized code

 
 
 

1.3.7 Lack of productivity

 
 
 

1.4 Chapter summary

 
 
sitemap

Unable to load book!

The book could not be loaded.

(try again in a couple of minutes)

manning.com homepage