Uploaded November 2025 | Updated November 2026, 14 hours ago
With James Mitchell.
Bad code isn’t just a phase—it’s a process. Over 25 years of programming, I’ve written code so flawed it could glitch out even a Pong clone. But along the way, I learned some crucial lessons about testing, performance, architecture, and design. This talk is a practical guide to identifying common pitfalls, improving your workflow, and making smarter coding decisions. Expect fewer war stories and more actionable takeaways, because the goal isn’t just to survive bad code—it’s to get better with each line you write.
Video courtesy of GCAP and IGEA
www.gcap.com.au
With James Mitchell.
Bad code isn’t just a phase—it’s a process. Over 25 years of programming, I’ve written code so flawed it could glitch out even a Pong clone. But along the way, I learned some crucial lessons about testing, performance, architecture, and design. This talk is a practical guide to identifying common pitfalls, improving your workflow, and making smarter coding decisions. Expect fewer war stories and more actionable takeaways, because the goal isn’t just to survive bad code—it’s to get better with each line you write.
Video courtesy of GCAP and IGEA
www.gcap.com.au










