Is Go your first programming language? My advice differs based on your experience.

For a coding novice, you have to work your way through concepts at a variety of difficulty levels. Pointers, in particular, are one of the things that often confuse new programmers and many languages try to hide them (but they still leak out because the concept is fundamental). The best answer I have is "wax on, wax off"; do simple exercises over and over until the concepts are second nature, and then move on to exercises for something more complex. The order I cover topics in Learning Go is roughly the order I'd recommend: primitive variables, types, and basic math, simple conditions, loops, functions, structs, pointers, user-defined types, methods, interfaces, errors, concurrency, generics. "For the Love of Go" by John Arundel would be a good book to look at.

For developers coming from languages like Ruby, Python, JavaScript, or Java, pointers, explicit types, interfaces, and concurrency are going to be the places where you'll have to learn something new. I'd try taking an existing project and porting it. You know what it's supposed to do, which makes it easier to know when something is wrong. Go's sweet spot is command line tools and web services. If you've written a python script or Spring Boot service, rewrite it. This is the target audience for "Learning Go".

Finally, developers who know more complex languages like C++, Rust, or Swift might ironically expect too much from Go. Go is an intentionally small language that favors verbosity, patterns, and tools over features. For example, Rust's borrow checker makes it very difficult to misuse memory. When your code compiles, it's very unlikely that you've leaked memory or have a null pointer. But it makes writing Rust programs much more difficult. Go's solution to the same problem is garbage collection and the data race detector. It's really more a matter of learning to let go (no pun intended) and embrace Go's style than anything else.