Every dev landing in Go goes through the same two phases: first “am I seriously writing if err != nil every three lines?” and then, a few months later, “ok, now I get why”. This Go error handling article exists to shorten the trip between the two. Errors are values Go has no exceptions flying […]
READ MORESeven articles in and you’ve been using Go slices without knowing what they really are. Today we pop the hood, because the difference between using Go and understanding Go lives exactly here: knowing what’s underneath a []int. Arrays: the foundations you rarely touch Go’s array is fixed size and behaves as a VALUE (A Tour […]
READ MORELast article interfaces were pure elegance. Today we visit the basement of Go type assertions: what happens when you need to recover the concrete type living inside an interface, what that ubiquitous any is, and the nil gotcha that has bitten every gopher at least once. The empty interface and any An interface with no […]
READ MORETraining is not feeding data to a machine and hoping. It is a process with rules. What training actually means Chapter 6 left four algorithms on the table and one phrase repeated without ever being unpacked, “it gets trained on the data”. Time to open that box. Training a model is the process by which […]
READ MORE