I’m pushing 40 and recently started systematically learning about machine learning and large models. It kind of feels like going back 16 years, right after I graduated, when I had all these dev paths to choose from—backend, frontend, Android, iOS. I actually did about half a year as an Android dev intern, but I ended up picking iOS. Not for any fancy reason—just because I loved the feel of it. I loved iOS, I loved the iPhone, and I could stay up all night tweaking a single UI control and feel fine with just a few hours of sleep the next day....

Introduction As a Go and Ruby on Rails (RoR) developer, I often find myself building microservices that interact with RoR applications. One of the most annoying challenges is maintaining simple data structures like maps or slices, especially when they need to evolve. For example, let’s take a look at how we define a slice of Partner structs: type Partner struct { Name string } func ListPartners() []Partner { return []Partner{ {Name: "partner1"}, {Name: "partner2"}, {Name: "partner3"}, {Name: "partner4"}, } } At first glance, this looks fine....

What is Channel If you’re a new Go developer, you’ve likely heard of or used a channel before. But what exactly is a channel, and what is its purpose? Before we delve deeper, let’s first discuss this. So, what is a channel? According to the official Go documentation, a channel is Channels are a typed conduit through which you can send and receive values with the channel operator, <-. basically, you can say that Channel is a communication mechanism....