Go Meetup #23 - Celebration of release Go 1.26

Hosted by Pure Storage
Please note at the Pure Storage office, all meetup attendees will be required to sign a generic NDA used for all office visitors to be able to attend the meetup.
Doors are open from 17:30, talks will start 18:00, and we have 2 talks and panel discussion.

1. Daniel Turecek (Pure Storage) - What is new in Go 1.26

In this lightning talk, we’ll tour what’s coming in Go 1.26 (based on the current draft release notes) and why it matters for real-world services. We’ll cover runtime and performance wins like the default Green Tea GC, faster cgo calls, improved stack allocation, and new profiling options aimed at spotting goroutine leaks. We’ll also look at security and crypto upgrades including 64-bit heap address randomization, the new `crypto/hpke` package, and post-quantum hybrid key exchange on by default in TLS. Finally, we’ll touch on pragmatic developer-experience changes—from `new(expr)` and richer generics constraints to tooling updates like `go fix`, `pprof` flame graphs by default, and compatibility-oriented module defaults.

2. Vilibald Wanca - Nail the Basics - S01E02

Good Go code starts with a simple, predictable layout. In this talk, we’ll cover the standard approach to structuring Go projects: keep things flat early on, map one package to one directory, and keep tests right next to the code they validate (like `user.go` and `user_test.go`). We’ll also look at common structural mistakes—such as over-engineering too soon or importing Java/Python-style layering that fights Go’s package model—and how to avoid them. Finally, you’ll leave with a handful of quick wins you can apply immediately: formatting and import automation with `gofmt`/`goimports`, stronger feedback loops with `golangci-lint`, and editor setups (VSCode Go extension or GoLand) that make the “Go way” feel effortless.

3. Panel discussion with our speakers on AI tools and Go development

Join us for a panel discussion with our speakers on how AI tools are changing Go development in practice. We’ll compare real workflows for using assistants to design, code, test, refactor, and review Go services—what actually saves time, what introduces risk, and where humans still need to stay firmly in the loop. Expect practical tips on prompt patterns, maintaining code quality, avoiding “AI-shaped” over-engineering, and integrating AI into existing tooling like linters, editors, and CI. Bring your questions—we’ll keep it candid, concrete, and Go-focused.