Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Sroop Sunar — The life-changing magic of tidying technical debt Contents 1:03 Marie Kondo and her books 3:10 “Technical debt does not spark joy” 3:45 The Big Ball of Mud 6:10 Clean code vs Tidy code 11:54 Applying the konmari method 16:08 2019 is a year if the empathetic programmer 17:22 "Deleting code is good, because all code is bad" 22:50 Conclusion 24:00 Questions and Answers Let's chat, meet, and share our ideas via all the social media: Join us on Facebook: https://bit.ly/2WjAgVb Tweet a bit with us there: https://bit.ly/2XmndyK Follow us on LinkedIn: https://bit.ly/2MmSn8j Hop in some cool articles here: https://bit.ly/2IcMgOx Our Instagram account: https://bit.ly/2QDZCaf Become a register member on our site and get all the benefits: https://bit.ly/313cImj
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 the video titled "The Life-Changing Magic of Tidying Technical Debt," Sroop Sunar explores the parallels between Marie Kondo's tidying philosophy and the world of software development, specifically focusing on technical debt. Sunar begins by introducing Marie Kondo as a globally recognized tidying expert, drawing attention to her methods that encourage mindfulness about possessions and the idea that only items that 'spark joy' should be kept. This sets the stage to discuss how technical debt in programming can clutter codebases, slow down development, and cause frustration among developers. Key points discussed include: - **Definition of Technical Debt**: Sunar explains that technical debt is akin to clutter in our lives, which can impede development processes. - **The Big Ball of Mud**: Referencing a 1997 paper by Brian Foote and Joseph Yoder, he describes this phenomenon of complex, tangled code that results from poor architecture and neglect over time. - **Clean Code vs Tidy Code**: He differentiates between clean code (which adheres to certain best practices) and tidy code (which focuses on the overall simplicity and maintainability of the codebase). - **Applying the Konmari Method**: Drawing on Kondo's principles, he outlines two crucial aspects: empathy towards developers and the importance of deleting unnecessary code to reduce complexity. - **Empathy in Development**: Emphasizing the need for empathy, Sunar suggests that understanding the emotional labor behind code helps reduce feelings of shame and anxiety about legacy code. - **The Importance of Deleting Code**: He notes that deleting code, although sometimes difficult emotionally, is crucial to preventing technical debt. Emptying one's codebase of unnecessary elements can lead to cleaner and more efficient systems. Significant examples include Sunar’s experience with the evolution of a codebase at his company, Peg, illustrating how the complexity of code can grow unchecked and result in a 'big ball of mud.' Sunar concludes that the combination of clean and tidy code practices can provide a significant uplift in developer productivity and satisfaction, encouraging a shift in mentality towards code deletion. He advocates adopting empathy as the fundamental skill for developers, insisting on the importance of acknowledging the challenging work that goes into code and the necessity to prune it for a healthier codebase. Overall, the presentation encapsulates a call to action for developers to embrace a tidier approach to software through practices that spark joy, such as empathy and decisive deletion.
Suggest modifications
Cancel
