Go in Production: patterns that survive fintech
Graceful shutdown, middleware stack, circuit breaker, structured logging. The Go patterns that survived months of regulated financial production.
Lessons learned, problems and solutions
Graceful shutdown, middleware stack, circuit breaker, structured logging. The Go patterns that survived months of regulated financial production.
CSS frustrates when you jump to styling before understanding space. It's learned in a precise order: selectors, box model, layout, responsive, animations. With an interactive course.
HTML is learned by building real pages, not by memorizing a list of tags. The right order, from structure to forms, with a free course to practice.
Go iterators explained through the real traps: the yield contract, the 'continued iteration' panic, cleanup on break, iter.Pull and its stop(), and when NOT to write an iterator.
Copy-paste Claude Code hook examples: auto-format after edits, block dangerous commands, and the Stop hook that forces a final check without an infinite loop. Real settings.json config.
Expose your API to Claude through a Go MCP server: the official SDK, stdio vs streamable HTTP, typed tools, auth, and the design mistakes to avoid in production.
Chaining order, recover, context timeouts, the ResponseWriter wrapping that breaks streaming, request IDs: the Go HTTP middleware that holds up in production, with real code and traps.
How I reworked 109 interactive lessons with 5 desirable difficulties (active recall, spaced repetition, the generation effect) and AI agents, all tested in production.
26 AI agents comb through my PHP media server in parallel: one vulnerability found, a bug my own fix introduced, and the best lesson — knowing when to stop.
What the neuroscience of learning says about coding with AI: cognitive debt, the illusion of competence, and the 4 mechanisms to actually retain instead of copy-pasting.