Go 1.23 introduced an inbuilt concept of \"iterators\" to the language, with some controversy. The \"signature\" & functional nature of these iterators has been hard to parse at first glance by quite a few Gophers. Let's take a look at a few concrete examples step-by-step to demystify those \"funcs that accept funcs that return bools\" & to see why this design makes sense.

One of the coolest features of Go is goroutines, and the fact that concurrency is part of the language. But concurrency normally requires synchronization, so... the sync package comes to the rescue. The sync package provides the main primitives of synchronization to use in tandem with the go concurrency, but... how does the sync package work? How are primitives like WaitGroup, Once, or Mutex built? We are going to explore that in this talk.

It's a guide through of how we build LLM-based features at incident.io - and how we take advantage of newer Golang features to achieve this.