A Crystal Ball to Prioritize Technical Debt
•
0 gostou•927 visualizações
Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/2pdF2OP. Adam Tornhill introduces an approach with the potential to change how we view software systems, offering an overview of techniques, based on software evolution and findings from various fields within psychology, that help uncover both problematic code and the social dimension of the teams that build software. He illustrates each point with a case study from a real-world codebase. Filmed at qconlondon.com. Adam Tornhill is the founder and CTO of Empear, where he designs tools for software analysis. He’s also the author of Your Code as a Crime Scene, has written the popular Lisp for the Web tutorial, and self-published a book on patterns in C.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais de C4Media
Mais de C4Media (20)
Último
Último (20)
A Crystal Ball to Prioritize Technical Debt
- 2. InfoQ.com: News & Community Site Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations /priority-technical-debt • Over 1,000,000 software developers, architects and CTOs read the site world- wide every month • 250,000 senior developers subscribe to our weekly newsletter • Published in 4 languages (English, Chinese, Japanese and Brazilian Portuguese) • Post content from our QCon conferences • 2 dedicated podcast channels: The InfoQ Podcast, with a focus on Architecture and The Engineering Culture Podcast, with a focus on building • 96 deep dives on innovative topics packed as downloadable emags and minibooks • Over 40 new content items per week
- 3. Purpose of QCon - to empower software development by facilitating the spread of knowledge and innovation Strategy - practitioner-driven conference designed for YOU: influencers of change and innovation in your teams - speakers and topics driving the evolution and innovation - connecting and catalyzing the influencers and innovators Highlights - attended by more than 12,000 delegates since 2007 - held in 9 cities worldwide Presented at QCon London www.qconlondon.com
- 4. “Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development” Questioning Technical Debt https://martinfowler.com/bliki/TechnicalDebt.html @AdamTornhill
- 5. Interest Rate Is A Function Of Time http://i.imgur.com/a8Xo4Hp.png @AdamTornhill
- 6. All Technical Debt Isn’t Equal @AdamTornhill
- 7. @AdamTornhill Most Technical Debt Isn’t Technical
- 8. There’s A Strong Link Between Technical Debt And The Organisation @AdamTornhill
- 9. Wish List: Information to Prioritize Technical Debt @AdamTornhill Where’s the Highest Interest Rate? Does the Architecture Support the way our System Evolves? Any Productivity Bottlenecks for Inter-Team Coordination?
- 10. Collective Intelligence Social information Time @AdamTornhill Uncover Evolutionary Patterns In A System Frequencies
- 11. Hotspots Where’s The Highest Interest Rate?
- 12. Hotspots - A Tool To Prioritize @AdamTornhill
- 13. Code Complexity Code Change Frequency Hotspot @AdamTornhill
- 14. Hotspots - A Tool To Prioritize Hotspots Hotspots
- 15. All Code is Equal …but some Code is more equal than others* * Sorry, George Orwell
- 16. Why Hotspots Work 1 Year in Roslyn (C#, VB) 6 Years of Erlang 12 Years of Ruby on Rails Each file in the system ChangeFrequency Reference: Your Code as a Crime Scene, ISBN:1680500384 Prioritize improvements here! Ignore the long tail
- 17. Hotspots
- 20. File Level Hotspots Function Level Hotspots X Ray Recommended functions to improve. Hotspots X-Ray
- 23. Supervise your Complexity Trends @AdamTornhill Warning Sign! Refactoring Increases again
- 24. Hotspots Summary Hotspots find the code with the highest interest rate. Hotspots work because all code isn’t equal. Supervise the Complexity Trend of your Hotspots.
- 25. Evaluate Your Architectural Patterns Does the Architecture Support the way our System Evolves?
- 26. Code is Auto-Destructive Art @AdamTornhill
- 27. Your System’s Tipping Point?
- 28. DRM Shared DRM/AMD … Specify Your Logical Components @AdamTornhill
- 29. Identify Hotspots on a (Micro)Service Level @AdamTornhill
- 30. FuelInjector Temporal Coupling Diagnostics Combustion Commit #1 Commit #2 Commit #3 Time @AdamTornhill Read More: http://www.empear.com/blog/software-revolution-part3/
- 31. Model Controller View Services ORM Repository SQL Change CouplingLayers: A Separation of Concerns General Observation: 30-70 % of all commits touch multiple layers @AdamTornhill
- 32. Supervise The Change Coupling Between Services @AdamTornhill Temporal Coupling (potentially across repository boundaries)
- 33. The Microservices Shotgun Surgery Pattern @AdamTornhill
- 34. Tools Evolution Radar http://reveal.inf.usi.ch/web/dambros/tools/evoradar.php CodeScene: free for open source (commercial) https://codescene.io/ Moose Platform: open source platform http://www.moosetechnology.org/ Code Maat: open source, text-only (GPL) https://github.com/adamtornhill/code-maat
- 35. Architecture Summary Identify your Architectural Hotspots. Know your System’s Tipping Point. Use Temporal Coupling to Evaluate your Architecture.
- 36. Meet The Social Side of Your Code Any Productivity Bottlenecks for inter-team coordination?
- 37. Process Loss Process Loss The Potential Productivity Individual Contributions Real Productivity Team Work @AdamTornhill
- 39. Fractal Value: M. D’Ambros, M. Lanza, and H Gall. Fractal Figures: Visualizing Development Effort for CVS Entities. Inter-Team Overlap Fractal Value 0 ~1.0 Views IntegrationTasks Backup Tests Measure Team Coordination Excess Parallel Work The Diffusion of Responsibility
- 40. Measuring Conway’s Law Architectural Pattern: Package by Feature Views Features @AdamTornhill Front-End Team Export Team Recommendations Team Ads Team Calculations Team Backup Team
- 41. Team Team Team Team Team Team Team Team Team Team Team Team The Perils of Feature Teams @AdamTornhill
- 42. Align Your Architecture and your Organisation @AdamTornhill
- 43. Make Decisions Influenced By Data @AdamTornhill
- 44. @AdamTornhill Time - The Hidden Dimension of Software Design http://www.empear.com/blog/software-revolution-part3/ The Day I Parsed A Monster http://www.empear.com/blog/parse-a-monster/ Read The Book: Your Code As A Crime Scene https://pragprog.com/book/atcrime/your-code-as-a-crime-scene CodeScene: The Analyses as a Service https://codescene.io/ adam.tornhill@empear.com
- 45. Watch the video with slide synchronization on InfoQ.com! https://www.infoq.com/presentations/priority- technical-debt