Uploaded July 2024 | Updated November 2026, 14 hours ago
With Adam Matthews of Lemonade Games.
In this talk, we’ll discuss both the benefits and costs of "morale programming" in the quality of life for a studio, its projects, and its team. Our exploration will touch on the dangers associated with misguided technical planning, those being the technical but more important emotional debt, the production and productivity costs, and that “sunk-cost fallacy” feeling every engineer is more than likely familiar with.
We’ll explore the not unfounded trope of the bitter engineer and ask why it’s such a pox on our profession. In doing so, we’ll outline the culpability seniors, leads and directors play in perpetuating this trope and some of the solutions they need to adopt in order to protect themselves and their teams from tremendous, often paralysing technical concerns that inevitably plague a project.
We’ll define new standards for “clean code” in an iconoclastic attack on old and propose new methods and principles leads can adopt for the benefit of themselves and their team. While this talk is skewed towards senior-level developers, programmers of all stripes will find value in the philosophies, principles and soft skills described within and come to understand the critical role they play in the morale of a studio, even in a studio of one.
Video courtesy of GCAP and IGEA
www.gcap.com.au
With Adam Matthews of Lemonade Games.
In this talk, we’ll discuss both the benefits and costs of "morale programming" in the quality of life for a studio, its projects, and its team. Our exploration will touch on the dangers associated with misguided technical planning, those being the technical but more important emotional debt, the production and productivity costs, and that “sunk-cost fallacy” feeling every engineer is more than likely familiar with.
We’ll explore the not unfounded trope of the bitter engineer and ask why it’s such a pox on our profession. In doing so, we’ll outline the culpability seniors, leads and directors play in perpetuating this trope and some of the solutions they need to adopt in order to protect themselves and their teams from tremendous, often paralysing technical concerns that inevitably plague a project.
We’ll define new standards for “clean code” in an iconoclastic attack on old and propose new methods and principles leads can adopt for the benefit of themselves and their team. While this talk is skewed towards senior-level developers, programmers of all stripes will find value in the philosophies, principles and soft skills described within and come to understand the critical role they play in the morale of a studio, even in a studio of one.
Video courtesy of GCAP and IGEA
www.gcap.com.au










