Thinking of using go for my next project
I have used javascript (nodejs) for my projects but I am hearing a lot about how go is better and faster. I have learned go so I am thinking of a new project using it.
Does anyone has experience building a project with go? What should I keep in mind any tips? Are unit tests necessary?
I really like Go! It is wonderful to work with as long as you're not averse to writing a lot of boilerplate yourself, especially when working in a full blown project.
One tip I would have is as you're planning out your project, make sure to check that key functionality is available in mature and active (important) packages unless you're going to be writing all of that yourself. Unlike the JS world where you are spoiled for choice there can be some lack of packages in certain areas in the world of Go.
As @melmarshall has mentioned, unit test where you feel it needs to be watertight but otherwise blanket coverage is rarely a bad thing and since it isn't really a Go specific problem feel free to experiment :)
Otherwise it has been super fun working with it in small applications so let me know how it goes for you!
I work on solo projects no team and I build heavy software with lots of functionality. I don't write much test only for important things like payments etc.
Should I still switch to go? I'm really confused
Go is great for projects where you need your code to run very quickly and concurrently. I think its ideal use case is backend data processing. I've used it to build click-tracking attribution software, where you need to process an event and redirect the user extremely quickly. It's a lot of fun to write!
I would unit test any business logic that has to be right or has tricky edge cases, e.g. calculating tax.
Is it good for solo developers?