Lifetime updates for free!
Nobody wants to buy a course only to find out it is out of date. That's why I am committed to providing updates to the course for free. No nickel and diming you for updates; if you purchase the course you will always have access to the most up-to-date version.
The course has been tested and verified to work with Go 1.23. As new version of Go are released, I will test and update the course as needed.
If you are using a newer version of Go and I haven't updated this page yet, the course code will almost certainly still work, but feel free to shoot me an email if you are unsure.
What do these updates include? Oftentimes the updates required for the course are minor. For instance, a library might make a breaking change and require a video showing how to upgrade versions. Or a best practice in Go might change, leading to an addendum to a video illustrating the modern way to write the code. When this happens, I can provide an update fairly quickly, as it only requires a new lesson being added to the course.
Other times the updates are more significant. For example, when Go introduced modules, the Go tooling changed pretty drastically. Changes like this can sometimes require a much larger change, as many lessons in the course are affected by the change. In cases like this it may take a bit longer to provide the updates, but I will provide them as quickly as possible.
What you shouldn't expect from me are updates purely for the sake of updating the course. One of the best parts about writing Go code is knowing that code you wrote 3+ years ago won't arbitrarily go out of date or stop working like it can in some other languages or frameworks. This is something to embrace and celebrate. If the code in the course still works and is idiomatic, it doesn't make sense to waste time updating it just so the video "appears" to be new. I would much rather spend that time creating new content for you to learn from. This is why the samples for the course appear to be 2+ years old - they are! But they still work and are still using idiomatic Go code, so even if I recreated the videos today, the code would look nearly identical.
If you have any questions, feel free to get in touch - jon@calhoun.io - and I'll be happy to answer any questions you have.