Lessons from two decades of writing bad code @GCAPConf
Lessons from two decades of writing bad code  @GCAPConf
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
Lessons from two decades of writing bad codeThe Wheels Fell Off So We Reinvented ThemWho Needs a DAW? — Synthesising Sounds at Runtime in MetaSoundsManaging UpEmpowering Design: The Tools and Pipelines of UnpackingLevel up your business with the Digital Games Tax OffsetOpening Keynote: 10 Years Crossing the Road: These Lanes Will Keep ChangingPitch Perfect: How to get noticed by PublishersThe Oceans of Crab God: An Artistic Deep DiveTop Ten FAQs about speaker submissions at GCAPMorale Code: Tools and Techniques for Technical LeadsFinding Home in the Music of Total War: Pharaoh
GCAP |

Lessons from two decades of writing bad code

SHARE TO X SHARE TO REDDIT SHARE TO FACEBOOK WALLPAPER