Dissolving Technical Debt on Agile Projects - Smidig 2012

•

1 recomendación•526 vistas

Experiences with dealing with legacy code while delivering value. Key points: 1) Legacy code costs a lot. 2) Design must be maintained & evolved. 3) Continous refactoring during each task is a way to achieve 2.

Tecnología

An Agile Approach to
Technical Debt
Is The Only Way

Jakub Holý @ iterate no

by Jon Baldock nz @ flickr

We've all been there - mess of code

by Ignaz Wiradi @ wikimedia

What we would like to have
- clean, structured, fitting

by cotallo-nonocot @ flickr

What we do have. It (likely) started with st. small & clean but requirements evolved
while the design of the code did not - only hacked & patched

God class
● 15 kLOC
● 300 properties
● 320 methods
● 50 constants
● used everywhere

by mandalinarossa @ flickr

Example of legacy - a typical monstrous god class that we were confronted with.

True cost of legacy

Pain <= Time wasted in code archeology, money & time wasted due to bugs being
introduced.
Legacy code matters to business for real money are wasted there.

Refactor!

The only way out is to improve the design

?

How do we get from L to R? The sad answer is we don't.
It took centuries to build R. We can never get from L to R in a reasonable time. There
is too much mess, too much to fix.

Code Churn

Michael Feathers: Getting Empirical about Refactoring

Code-churn driven refactoring: improve where it matters & pays off most - complex &
changed often

=> Boy Scout Refactoring
● Only task-related
● Time-boxed
● Always
● (+ TDD)

Refactoring can go on forever => focus, time-box. Task related => in code that
matters most now/in near future. (We: 1/3 every task devoted to refactoring.)

Refactoring: Improving the Design of Existing
Code
Martin Fowler

Working Effectively with Legacy Code
Michael Feathers

Behead Your Legacy Beast: The Mikado
Method
D. Brolund, O. Ellnestam

True cost of legacy

Show to your management; Legacy code = lot of money lost.

Challenge
Large-scale refactorings
● risky => avoid
● sometimes necessary
● boy scout rule doesn't help

Summary
● Design needs love
● Continuous, focused, time-boxed refactoring
● True cost of legacy

Recommended

Retrospectives: Group code reviews:

改 Observe
Evaluate
Teach
Learn
善 Adjust Unify

Something that worked great for us

Questions?

@HolyJak
jakub.holy@iterate.no
theholyjava.wordpress.com

Más contenido relacionado

Similar a Dissolving Technical Debt on Agile Projects - Smidig 2012

Devconf 2011 - PHP - How Yii framework is developed

Alexander Makarov

The ninth principle from the Agile Manifesto states that technical excellence enhances agility, but when the codebase is ugly and the deadlines are tight, most teams don’t choose to refactor mercilessly, adopt TDD, or evaluate automated testing tools—unless they have the proper support. In our experience working with multiple teams in a single codebase, developers can feel victim to a legacy codebase if only a few people are writing clean code or refactoring; guiding them on how to decrease technical debt while delivering their projects helps "unstuck" their other agile practices. We will talk about the challenges we’ve seen with Product Owners, Managers, and Scrum Masters interacting with teams at various stages of agile+technical excellence and how a focus on technical practices sparked a wider interest in craftsmanship. Learn how can you influence the team towards the right practices while fostering their sense of ownership. Getting serious about technical excellence requires support from technical and non-technical roles, and we’ll share how we partnered as coaches to help an organization through a technical turnaround with some tips for others who need to do the same.

Technical Excellence Doesn't Just Happen--Igniting a Craftsmanship Culture

Allison Pollard

Big Ball of Mud (BBoM) architectures are viewed as the culmination of many design decisions that, over time, result in a system that is hodgepodge of steaming and smelly anti-patterns. It can be arguably claimed that one of the reasons for the growth and popularity of agile practices is partially due to the fact that the state of the art of software architectures was not that good. Being agile, with its focus on extensive testing and frequent integration, has shown that it can make it easier to deal with evolving architectures (possibly muddy) and keeping systems working while making significant improvements and adding functionality. Time has also shown that Agile practices are not sufficient to prevent or eliminate Mud. It is important to recognize what is core to the architecture and the problem at hand when evolving an architecture. This talk will examine the paradoxes that underlie Big Balls of Mud, what causes them, and why they are so prominent. I’ll explore what agile practices can help us avoid or cope with mud. I’ll also explain why continuous delivery and TDD with refactoring is not enough to help ensure clean architecture and why it is important to understand what is core to the architecture and the problem at hand. Understanding what changes in the system and at what rates can help you prevent becoming mired in mud. By first understanding where a system’s complexities are and where it keeps getting worse, we can then work hard (and more intelligently) at sustaining the architecture. This can become a key value to the agile team. The results will leave attendees with practices and patterns that help clean your code (refactor) as well as keeping the code clean or from getting muddier. Additionally, I’ll talk about some practices and patterns that help keep the code clean or from getting muddier. Some of these include: Testing, Divide & Conquer, Gentrification, Demolition, Quarantine, Refactoring, Craftmanship and the like.. The original Big Ball of Mud paper described some best practices such as SHEARING LAYERS and SWEEPING IT UNDER THE RUG as a way to help deal with muddy architectures. Additionally there are some other practices such as PAVING OVER THE WAGON TRAIL and WIPING YOUR FEET AT THE DOOR that can make code more habitable.

Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work

Joseph Yoder

Code Refactoring - Live Coding Demo (JavaDay 2014)

Peter Kofler

Technical Excellence Doesn't Just Happen - AgileIndy 2016

Allison Pollard

Have you always heard about refactor and it always sounded like a foreign language to you? Have you tried to change code several times but found it impossible to make such changes in several projects? Do you feel overwhelmed when working with legacy code? Let's see the benefits of refactoring your code and see some tips on how to do it safely! We will start talking about what is legacy code, what we understand about refactoring and why it is so important nowadays when in most cases we work with software that others have written. Later we will share when we should start thinking on refactoring code and next we will see some recommended techniques to work with legacy code, which will even help us to know where to start and how. And finally, we will see in a live coding session some of the most important and useful refactoring techniques we could apply in our day-to-day job  At the end of this session, I hope you may have learned some tips on how to work with legacy code and how to apply certain techniques to make your day to day more enjoyable ;-) === * Presentation shared at Jconf Mexico (October 3rd, 2020) - https://convoca.dev/jconf-mexico-2020/talk/FMDT8Z/ and revisited and updated for sharing at JConf Centro América (December 5th, 2020) https://hopin.to/events/jconf-centroamerica-2020

Refactor your code: when, why and how (revisited)

Nacho Cougil

Coding Dojo for Testers/Testing Dojo: Designing Test Cases with FitNesse (2014)

Peter Kofler

Deliberate Practice (2014)

Peter Kofler

Legacy Code. I never wrote it; everybody else did! How many times have you waded through an ageing, decaying, tangled forrest of code and wished it would just die? How many times have you heard someone say that what really needs to happen is a complete rewrite? I have heard this many times, and, have uttered that fatal sentence myself. But shouldn’t we love our legacy code? Doesn’t it represent our investment and the hard work of ourselves and our predecessors? Throwing it away is dangerous, because, before we do, we’ll need to work out exactly what it does, and we’ll need to tweeze out that critical business logic nestled in a deeply entangled knot of IF statements. It could take us years to do, and we’ll have to maintain two systems whilst we do it, inevitably adding new features to them both. Yes we get to reimplement using the latest, coolest programming language, instead of an old behemoth, but how long will our new cool language be around, and who will maintain that code, when it itself inevitably turns to legacy? We can throw our arms in the air, complaining and grumbling about how we didn’t write the code, how we would never have written it the way it is, how those that wrote it were lesser programmers, possibly lesser humans themselves, but the code still remains, staring us in the face and hanging around for longer that we could possibly imagine. We can sort it out, we can improve it, we can make it testable, and we can learn to love our legacy code.

How I Learned to Stop Worrying and Love Legacy Code.....

Mike Harris

Workshop fight legacy code write unit test

Tung Nguyen Thanh

[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]

Agile đây Vietnam

The bigrewrite

Codecamp Romania

"Why should we write our tests first? Isn't that going to slow my development?" "What? Assigning a single task to 2 developers? How is that efficient? What a waste of resources!" "Look, in the perfect world your advises are great, but I have a project to finish here." In this talk Marcello explores efficiency in contrast to effectiveness. He looks into how practices, traditionally accepted as efficient, sometimes turn out to be less effective than a few "impractical" things he has come across.

Pair Programming, TDD and other impractical things

Marcello Duarte

Effective entrepreneurship for developers

Carlos Ble

The bigrewrite

Codecamp Romania

From Journeyman to Master

Angad Singh

Our industry has a problem: We are not lacking software methodologies, programming languages, tools or frameworks but we need great software engineers. Great software engineer teams build quality-in and deliver great software on a regular basis. The technical excellence of those engineers will help you escape the "Waterfall sandwich" and make your organization a little more agile, from the inception of an idea till they go live. I will talk about my experiences from the last 15 years, including small software delivery teams until big financial institutions. Why would a company like to be "agile"? How can a company achieve that? How can you achieve Technical Excellence in your software teams? What developer skills are more important than languages, methods or frameworks? This will be an interactive session with a Q&A at the end.

Achieving Technical Excellence in Your Software Teams - from Devternity

Peter Gfader

Docker is killing your #devops Efforts

Kris Buytaert

Coding Dojo Firenze - vol1

Massimo Iacolare

Designing Test Cases for the Gilded Rose Kata (2013)

Peter Kofler

Similar a Dissolving Technical Debt on Agile Projects - Smidig 2012 (20)

Devconf 2011 - PHP - How Yii framework is developed

Technical Excellence Doesn't Just Happen--Igniting a Craftsmanship Culture

Taming Big Balls of Mud with Diligence, Agile Practices, and Hard Work

Code Refactoring - Live Coding Demo (JavaDay 2014)

Technical Excellence Doesn't Just Happen - AgileIndy 2016

Refactor your code: when, why and how (revisited)

Coding Dojo for Testers/Testing Dojo: Designing Test Cases with FitNesse (2014)

Deliberate Practice (2014)

How I Learned to Stop Worrying and Love Legacy Code.....

Workshop fight legacy code write unit test

[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]

The bigrewrite

Pair Programming, TDD and other impractical things

Effective entrepreneurship for developers

The bigrewrite

From Journeyman to Master

Achieving Technical Excellence in Your Software Teams - from Devternity

Docker is killing your #devops Efforts

Coding Dojo Firenze - vol1

Designing Test Cases for the Gilded Rose Kata (2013)

Último

In an era where artificial intelligence (AI) stands at the forefront of business innovation, Information Architecture (IA) is at the core of functionality. See “There’s No AI Without IA” – (from 2016 but even more relevant today) Understanding and leveraging how Information Architecture (IA) supports AI synergies between knowledge engineering and prompt engineering is critical for senior leaders looking to successfully deploy AI for internal and externally facing knowledge processes. This webinar be a high-level overview of the methodologies that can elevate AI-driven knowledge processes supporting both employees and customers. Core Insights Include: Strategic Knowledge Engineering: Delve into how structuring AI's knowledge base is required to prevent hallucinations, enable contextual retrieval of accurate information. This will include discussion of gold standard libraries of use cases support testing various LLMs and structures and configurations of knowledge base. Precision in Prompt Engineering: Learn the art of crafting prompts that direct AI to deliver targeted, relevant responses, thereby optimizing customer experiences and business outcomes. Unified Approach for Enhanced AI Performance: Explore the intersection of knowledge and prompt engineering to develop AI systems that are not only more responsive but also aligned with overarching business strategies. Guiding Principles for Implementation: Equip yourself with best practices, ethical guidelines, and strategic considerations for embedding these technologies into your business ecosystem effectively. This webinar is designed to empower business and technology leaders with the knowledge to harness the full potential of AI, ensuring their organizations not only keep pace with digital transformation but lead the charge. Join us to map a roadmap to fully leverage Information Architecture (IA) and AI chart a course towards a future where AI is a key pillar of strategic innovation and business success.

EIS-Webinar-Prompt-Knowledge-Eng-2024-04-08.pptx

Earley Information Science

The 7 Things I Know About Cyber Security After 25 Years | April 2024

Rafal Los

The presentation explores the development and application of artificial intelligence (AI) from its inception to its current status in the modern world. The term "artificial intelligence" was first coined by John McCarthy in 1956 to describe efforts to develop computer programs capable of performing tasks that typically require human intelligence. This concept was first introduced at a conference held at Dartmouth College, where programs demonstrated capabilities such as playing chess, proving theorems, and interpreting texts. In the early stages, Alan Turing contributed to the field by defining intelligence as the ability of a being to respond to certain questions intelligently, proposing what is now known as the Turing Test to evaluate the presence of intelligent behavior in machines. As the decades progressed, AI evolved significantly. The 1980s focused on machine learning, teaching computers to learn from data, leading to the development of models that could improve their performance based on their experiences. The 1990s and 2000s saw further advances in algorithms and computational power, which allowed for more sophisticated data analysis techniques, including data mining. By the 2010s, the proliferation of big data and the refinement of deep learning techniques enabled AI to become mainstream. Notable milestones included the success of Google's AlphaGo and advancements in autonomous vehicles by companies like Tesla and Waymo. A major theme of the presentation is the application of generative AI, which has been used for tasks such as natural language text generation, translation, and question answering. Generative AI uses large datasets to train models that can then produce new, coherent pieces of text or other media. The presentation also discusses the ethical implications and the need for regulation in AI, highlighting issues such as privacy, bias, and the potential for misuse. These concerns have prompted calls for comprehensive regulations to ensure the safe and equitable use of AI technologies. Artificial intelligence has also played a significant role in healthcare, particularly highlighted during the COVID-19 pandemic, where it was used in drug discovery, vaccine development, and analyzing the spread of the virus. The capabilities of AI in healthcare are vast, ranging from medical diagnostics to personalized medicine, demonstrating the technology's potential to revolutionize fields beyond just technical or consumer applications. In conclusion, AI continues to be a rapidly evolving field with significant implications for various aspects of society. The development from theoretical concepts to real-world applications illustrates both the potential benefits and the challenges that come with integrating advanced technologies into everyday life. The ongoing discussion about AI ethics and regulation underscores the importance of managing these technologies responsibly to maximize their their benefits while minimizing potential harms.

Artificial Intelligence: Facts and Myths

Joaquim Jorge

GenCyber Cyber Security Day Presentation

Michael W. Hawkins

BooK Now Call us at +918448380779 to hire a gorgeous and seductive call girl for sex. Take a Delhi Escort Service. The help of our escort agency is mostly meant for men who want sexual Indian Escorts In Delhi NCR. It should be noted that any impersonator will get 100 attention from our Young Girls Escorts in Delhi. They will assume the position of reliable allies. VIP Call Girl With Original Photos Book Tonight +918448380779 Our Cheap Price 1 Hour not available 2 Hours 5000 Full Night 8000 TAG: Call Girls in Delhi, Noida, Gurgaon, Ghaziabad, Connaught Place, Greater Kailash Delhi, Lajpat Nagar Delhi, Mayur Vihar Delhi, Chanakyapuri Delhi, New Friends Colony Delhi, Majnu Ka Tilla, Karol Bagh, Malviya Nagar, Saket, Khan Market, Noida Sector 18, Noida Sector 76, Noida Sector 51, Gurgaon Mg Road, Iffco Chowk Gurgaon, Rajiv Chowk Gurgaon All Delhi Ncr Free Home Deliver

08448380779 Call Girls In Civil Lines Women Seeking Men

Delhi Call girls

Data Cloud, More than a CDP by Matt Robison

Anna Loughnan Colquhoun

GenAI Risks & Security Meetup 01052024.pdf

lior mazor

How to convert PDF to text with Nanonets

naman860154

In this session, we will delve into strategic approaches for optimizing knowledge management within Microsoft 365, amidst the evolving landscape of Copilot. From leveraging automatic metadata classification and permission governance with SharePoint Premium, to unlocking Viva Engage for the cultivation of knowledge and communities, you will gain actionable insights to bolster your organization's knowledge-sharing initiatives. In this session, we will also explore how to facilitate solutions to enable your employees to find answers and expertise within Microsoft 365. You will leave equipped with practical techniques and a deeper understanding of how there is more to effective knowledge management than just enabling Copilot, but building actual solutions to prepare the knowledge that Copilot and your employees can use.

Strategies for Unlocking Knowledge Management in Microsoft 365 in the Copilot...

Drew Madelung

Automating Google Workspace (GWS) & more with Apps Script

wesley chun

presentation ICT roal in 21st century education

jfdjdjcjdnsjd

Enterprise Knowledge’s Urmi Majumder, Principal Data Architecture Consultant, and Fernando Aguilar Islas, Senior Data Science Consultant, presented "Driving Behavioral Change for Information Management through Data-Driven Green Strategy" on March 27, 2024 at Enterprise Data World (EDW) in Orlando, Florida. In this presentation, Urmi and Fernando discussed a case study describing how the information management division in a large supply chain organization drove user behavior change through awareness of the carbon footprint of their duplicated and near-duplicated content, identified via advanced data analytics. Check out their presentation to gain valuable perspectives on utilizing data-driven strategies to influence positive behavioral shifts and support sustainability initiatives within your organization. In this session, participants gained answers to the following questions: - What is a Green Information Management (IM) Strategy, and why should you have one? - How can Artificial Intelligence (AI) and Machine Learning (ML) support your Green IM Strategy through content deduplication? - How can an organization use insights into their data to influence employee behavior for IM? - How can you reap additional benefits from content reduction that go beyond Green IM?

Driving Behavioral Change for Information Management through Data-Driven Gree...

Enterprise Knowledge

08448380779 Call Girls In Friends Colony Women Seeking Men

Delhi Call girls

Building Digital Trust in a Digital Economy Veronica Tan, Director - Cyber Security Agency of Singapore Apidays Singapore 2024: Connecting Customers, Business and Technology (April 17 & 18, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays Singapore 2024 - Building Digital Trust in a Digital Economy by Veron...

apidays

Histor y of HAM Radio presentation slide

vu2urc

Discord is a free app offering voice, video, and text chat functionalities, primarily catering to the gaming community. It serves as a hub for users to create and join servers tailored to their interests. Discord’s ecosystem comprises servers, each functioning as a distinct online community with its own channels dedicated to specific topics or activities. Users can engage in text-based discussions, voice calls, or video chats within these channels. Understanding Discord Servers Discord servers are virtual spaces where users congregate to interact, share content, and build communities. Servers may revolve around gaming, hobbies, interests, or fandoms, providing a platform for like-minded individuals to connect. Communication Features Discord offers a range of communication tools, including text channels for messaging, voice channels for real-time audio conversations, and video channels for face-to-face interactions. These features facilitate seamless communication and collaboration. What Does NSFW Mean? The acronym NSFW stands for “Not Safe For Work,” indicating content that may be inappropriate for professional or public settings. NSFW Content NSFW content encompasses material that is sexually explicit, violent, or otherwise graphic in nature. It often includes nudity, profanity, or depictions of sensitive topics.

Understanding Discord NSFW Servers A Guide for Responsible Users.pdf

UK Journal

08448380779 Call Girls In Diplomatic Enclave Women Seeking Men

Delhi Call girls

Axa Assurance Maroc - Insurer Innovation Award 2024

The Digital Insurer

[2024]Digital Global Overview Report 2024 Meltwater.pdf

hans926745

This presentations targets students or working professionals. You may know Google for search, YouTube, Android, Chrome, and Gmail, but did you know Google has many developer tools, platforms & APIs? This comprehensive yet still high-level overview outlines the most impactful tools for where to run your code, store & analyze your data. It will also inspire you as to what's possible. This talk is 50 minutes in length.

Powerful Google developer tools for immediate impact! (2023-24 C)

wesley chun

Dissolving Technical Debt on Agile Projects - Smidig 2012

1. An Agile Approach to Technical Debt Is The Only Way Jakub Holý @ iterate no

2. Origins

3. by Jon Baldock nz @ flickr We've all been there - mess of code

4. by Ignaz Wiradi @ wikimedia What we would like to have - clean, structured, fitting

5. by cotallo-nonocot @ flickr What we do have. It (likely) started with st. small & clean but requirements evolved while the design of the code did not - only hacked & patched

6. God class ● 15 kLOC ● 300 properties ● 320 methods ● 50 constants ● used everywhere by mandalinarossa @ flickr Example of legacy - a typical monstrous god class that we were confronted with.

7. The pain! It was pain!

8. True cost of legacy Pain <= Time wasted in code archeology, money & time wasted due to bugs being introduced. Legacy code matters to business for real money are wasted there.

9. Escape???

10. Refactor! The only way out is to improve the design

11. ? How do we get from L to R? The sad answer is we don't. It took centuries to build R. We can never get from L to R in a reasonable time. There is too much mess, too much to fix.

12. Code Churn Michael Feathers: Getting Empirical about Refactoring Code-churn driven refactoring: improve where it matters & pays off most - complex & changed often

13. => Boy Scout Refactoring ● Only task-related ● Time-boxed ● Always ● (+ TDD) Refactoring can go on forever => focus, time-box. Task related => in code that matters most now/in near future. (We: 1/3 every task devoted to refactoring.)

14. Refactoring: Improving the Design of Existing Code Martin Fowler Working Effectively with Legacy Code Michael Feathers Behead Your Legacy Beast: The Mikado Method D. Brolund, O. Ellnestam

15. It worked!

16. Required: Management endorsement

17. True cost of legacy Show to your management; Legacy code = lot of money lost.

18. Challenge Large-scale refactorings ● risky => avoid ● sometimes necessary ● boy scout rule doesn't help

19. Summary ● Design needs love ● Continuous, focused, time-boxed refactoring ● True cost of legacy

20. You too can do it!

21. Recommended Retrospectives: Group code reviews: 改 Observe Evaluate Teach Learn 善 Adjust Unify Something that worked great for us

22. Questions? @HolyJak jakub.holy@iterate.no theholyjava.wordpress.com

Dissolving Technical Debt on Agile Projects - Smidig 2012

Recomendados

Recomendados

Más contenido relacionado

Similar a Dissolving Technical Debt on Agile Projects - Smidig 2012

Similar a Dissolving Technical Debt on Agile Projects - Smidig 2012 (20)

Último

Último (20)

Dissolving Technical Debt on Agile Projects - Smidig 2012