guides VS gobyexample

Write a more complicated test later. Or refactor the test later. When you're in the moment, you want a test that works. Avoid hard coded values in completed tests, but use them when you're making sure your test doesn't break the very time you write it. A failing test is the starting point of the last decision you made, not the final product. Even if the imaginary people who are going to make fun of your code and call you stupid (ignore this if you're not relating, but if you are read this or watch it) are looking at your public github repo, they're not going to your test suites first. That would be insane. So you can be clunky at first.

GoByExamples: Offers clear, annotated examples for quick learning.

Go by example

I am not expend much time explaining things abouts golang sintax so i assume that you have go installed, you have basic knowledge of the language and at least create some basic project, if you need a refresh take a look here https://gobyexample.com/.

Some similar resources I like:

"Learn Go with Tests" book: https://quii.gitbook.io/learn-go-with-tests

"Go by Example": https://gobyexample.com/

Lately I've been learning go and I'm really liking it so far. I think Go fits the needs of a JavaScript programmer that wants to go lower level but not as low as c/c++.Currently I'm using Go by example for learning purposes.

Go By Example

I'm currently learning go and I would recommend this

here's a good start http://gobyexample.com