By default, Go auto-aliases your imports i.e you reference only the last part of the import path /internal/service/payment -> payment package and you can end up with a lot of packages having the same label. This talk goes through some of the iterations I went through, the tradeoffs, some references I looked at (stdlib + kubernetes) and where I'm currently at, I think I've got something pretty good with some extra hidden benefits.

This talk provides an in-depth technical overview of these impactful new packages. First, we will examine the new experimental encoding/json/v2, analyzing the significant performance improvements from its redesigned, allocation-optimized decoder and the flexible new API that addresses long-standing limitations of its predecessor.

Next, the talk will address the challenge of creating reliable tests for concurrent code by mastering the testing/synctest package. We will demonstrate how its isolated \"bubble\" environment with a virtualized clock provides a new paradigm for writing fast, simple, and deterministic tests for complex concurrent logic, effectively eliminating a common source of test flakiness.

A high level look at what Dojo does, plus "when", "how" and "why" we chose Go, for which systems we use it, and our experience with it so far.