Shout out to my wife who makes these hilarious thumbnails, follow her on Twitter [https://twitter.com/bonecloset] for more art stuff. CLI applications are extremely handy to use. Building out a lot of the nice features that good CLI apps have can be a bit time-consuming though. At least,

Shout out to my wife who makes these hilarious thumbnails, follow her on Twitter [https://twitter.com/bonecloset] for more art stuff. You can get quite far configuring your go programs with the standard library. You can read in your config file, or pass in arguments and parse them with

Go added a neat feature in 1.13 that they call error chains Errors can now implement a method called Unwrap that should return another error. Typically, this is an error that occurred further down in the call stack. It is very common in go to have errors get tossed

Error handling in Go is pretty straightforward. There are no exceptions, there are no try-catch blocks, there is only ERROR. Error is a type like any other primitive built into the language, like an int or a string. This makes error handling, while a tad verbose, very straightforward and easy

Go actually has a template package in its standard library, which is pretty sweet. Normally, this is something you see in separate 3rd party libraries or included in full frameworks, such as Laravel or Rails. It's very powerful too. In addition to injecting your data into templates, you can extend

Managing dependencies in go used to be a mess. There were about 3-4 widely used packages to manage dependencies, which sometimes made it weird to work on another codebase that used a different dependency management tool. Finally, in 1.11, go included its own dependency management tool called go modules.

Despite not having Object-Oriented Programming (OOP) language features, Go does have interfaces. Interfaces allow you to interchange what data types you are passing as arguments to a function, as long as that type has the required methods. Interfaces in Go are different compared to, say, C# or Java, in that

For my next go tutorial, I decided to actually demonstrate how to create a program. In this case, a REST API. But not just any REST API, oh no. This one is built using only the standard package library available in go. While there are really nice resources for doing

My second programming tutorial on Golang, this time on the basics of its concurrency primitives. I applied some of the feedback from the first video and applied it to this one. I contemplated talking about a few concurrency patterns commonly used in this video but decided it would be better

I made my first "comprehensive" video tutorial relating to programming. In this one, I explain how to utilize the basic language features of go, as fast as I can, without making tons of mistakes. I want to make more and better video tutorials like this one and would greatly appreciate

I recently started building up a lot of small little go packages that will lead up to a more comprehensive automated video editing tool I want to build. While creating these small packages, I wanted to create a simple CLI program to interact with each and do it more properly