Some of the more popular examples include: OpenFaaS - Serverless Framework, inlets - network tunnel, k3sup - Kubernetes installer and arkade - Kubernetes marketplace and CLI downloader. I certainly haven't worked at Google, and I haven't spoken at Gophercon, but I do use the language on a daily basis and maintain several popular open source projects used in production by companies small and large. You may ask who I am to write a book on Go. Why write a book?Ī sample from the ePub version, displayed on my MacBook. Oftentimes the purpose was to help onboard new open source contributors, or to publish something I had learned.Įveryday Go is a fast-track for learning concepts and techniques that you can apply to your everday day work and projects. They were practical and served a purpose. There are various blog posts I've published that get a lot of hits, but they were never about teaching the fundamentals like structs and variable types. Most of what I learned was through trial and error, or reading other codebases, but I also list books that I found helpful at the time.
#Goland cost code
Sometimes it was not comfortable being told "Your code is not idiomatic", but it only spurred me on. I started my journey with the language in around 2015, when I had a strong interest in contributing to and learn about Docker.Īs I learned, I noticed that my Go started off looking like the last language I'd used, but over time it improved. If you've ever searched for "Golang unit-testing", then you may have found one of my tutorials or videos about Go. I wanted to share the news with you, what to expect and a bit about the story behind it. Today I've published my first eBook on Go called "Everyday Golang".
0 kommentar(er)
