Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
RubyConf 2019 - Seven Deadly Sins by Brian McElaney Software projects accumulate many kinds of debt. Each debt comes in the form of small qualitative shortcomings we (knowingly or unknowingly) choose to ignore in the name of shipping. They cause friction -- and over time they can combine to easily grind momentum to a halt if left unchecked. While these kinds of debt can in fact be useful (if not necessary) to creating software - teams need to understand the nature of their shortcomings to prevent "velocity bankruptcy." In this talk we'll discuss the nature of process debt by using classical ideas related to "unproductive behavior" as a guide: hitting on shortcomings in culture, empathy, discipline, morale, organization, preparedness, and requirements. We'll discuss examples, tips on identifying the risks in your own projects, and how to decide when to avoid, mitigate, or accept and track these risks. #rubyconf2019 #confreaks
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In his talk "Seven Deadly Sins" at RubyConf 2019, Brian McElaney discusses the various forms of 'debt' that software projects accumulate, particularly focusing on process debt, which he argues is often more damaging than technical debt. He draws parallels between these debts and the seven deadly sins, using them as a framework to explore unproductive behaviors in development teams. Key points discussed include: - **Anger**: He details how project pressures lead to unproductive reactions, exemplified by a failed project with multiple teams lacking proper coordination, resulting in requirements oversight and eventual project cancellation. - **Desire**: McElaney warns against unchecked ambition in teams, sharing an experience where excessive effort on a challenging feature led to burnout and project failure—not due to lack of capability, but mismanagement of team morale. - **Envy**: This sin highlights the risks of seeing users as outsiders. He discusses a transportation project that failed to consider user contexts, leading to alienation instead of engagement. - **Gluttony**: The profligate use of advanced coding patterns without stemming from user needs can create compatibility issues within a project. He stresses the importance of cohesive processes. - **Greed**: Focusing on cost-cutting measures can lead businesses to miss value-adding opportunities, asserting the need to balance cost and quality in development. - **Pride**: McElaney points out the dangers of over-reliance on fast developers, where their isolated contributions can create knowledge gaps in the team, underscoring the need for collaboration and code reviews. - **Sloth**: He emphasizes the importance of strategic decision-making and architecture planning during software development. In closing, McElaney encourages teams to build processes that allow for collective reflection and realignment toward user needs, relational dynamics in projects, and healthy developer engagement. He emphasizes that by recognizing and naming these debts, teams can regain control of their development processes and avoid detrimental outcomes.
Suggest modifications
Cancel
