This series follows one engineer, Bill, refactoring real projects in Go, in hour-long sessions that show the actual decision-making behind each change rather than just a clean before-and-after. The value is in the why: what made a piece of code worth changing, and why he chose one approach over another.
Who this is for
It's aimed at engineers looking to sharpen their Go skills at a more advanced level, and works best with some background already in place:
- A computer science background, or at least two years of full-time professional programming experience
- Solid understanding of structural and object-oriented programming
- Hands-on experience with data structures like arrays, lists, queues, and stacks
- General awareness of processes, threads, and synchronization
11 lessons of real refactoring work, aimed squarely at engineers who want to see expert-level judgment applied to actual code, not just theory about clean code.