Your project is Legacy already, you just don't know it yet

In questo talk vorremmo esplorare alcuni fattori invisibili che, indipendentemente da metodologie agili di gestione, possono compromettere la buona riuscita di un progetto nel lungo periodo.

Vorremmo proporre il nostro punto di vista come developer sulla percezione della qualità di un progetto e sul perché non esista un rapporto causa effetto tra "working software" e "better software".

Come risvolti pratici esploreremo alcune metriche intrinseche del software da cui poter ottenere un giudizio imparziale sulla sua qualità. Spiegheremo quindi quale sia l'impatto di questi fattori invisibili sul successo di un progetto e sulla felicità delle persone coinvolte.

Transcript

1. LEGACY ALREADY Better Software Firenze, 11 Nov 2013 @arkh4m ~ @mat_jack1 YOUR PROJECT IS (YOU JUST DON’T KNOW IT YET)
2. WE ARE JU & MATTEO. WE ARE HAPPY SOFTWARE ENGINEERS, WORKING AT WELAIKA & CANTIERE CREATIVO HELLO
3. LET’S TALK ABOUT LEGACY {
4. A gift by will, especially of money or other personal property Legacy, noun
5. Heritage | Eredità
6. A software which is no longer mantained or supported Legacy Software
7. Nightmare | Incubo
8. DEVELOPERS HATE LEGACY We’re no exception.
9. UNCLEAR JUST STUPID A BIG BALL OF MUD
11. THE OLD CODE IS A MESS, WE NEED TO REWRITE IT “ ”
12. LOVE TO WRITE NEW CODE HATE TO READ CODE WHY SO? Developers…
13. IT’S HARDER TO READ CODE THAN TO WRITE IT The Fundamental Law of Software — Joel Spolsky
14. IT’S MUCH HARDER TO LISTEN THAN IT IS TO SPEAK The Fundamental Law of Life
15. THE OLD CODE IS A MESS, WE NEED TO REWRITE IT “ ”
16. OLD SUCKS “ ”
17. CODE DOESN’T RUST
18. LEGACY IS GOOD
19. HAS BEEN USED HAS BEEN TESTED BUGS WERE FOUND AND FIXED Legacy Code
20. SOFTWARE IS USEFUL WHEN IT SOLVES PROBLEMS The Value of Software
21. WHEN SOFTWARE IS USED AND IT WORKS, IT IS GOOD Good Software
22. IN TIME, GOOD SOFTWARE CAN BECOME LEGACY
23. BAD SOFTWARE JUST DIES
24. LET’S HOPE OUR PROJECTS WILL BE “LEGACY” ONE DAY
25. SO LEGACY IS COOL?
26. NOT REALLY.
27. SOFTWARE IS VALUABLE WHEN IT IS EASY TO CHANGE The Value of Software, Part II — Robert Martin
28. LEGACY SOFTWARE IS HORRIBLY HARD TO CHANGE
29. A LEGACY TALE {
30. You are managing a healthy project, along with a seasoned developer.
31. You are managing a healthy project, along with a seasoned developer. You fully embraced the Agile Way™ with standup sessions, sprint plannings, TDD, continuos integration, etc.
32. You are managing a healthy project, along with a seasoned developer. You fully embraced the Agile Way™ with standup sessions, sprint plannings, TDD, continuos integration, etc. The developer is pushing features like crazy, the client is happy, everything’s great.
33. Out of nowhere, your developer leaves your project.
34. Out of nowhere, your developer leaves your project. You find two new developers, a junior and a senior. They are very excited to join your project.
35. Out of nowhere, your developer leaves your project. You find two new developers, a junior and a senior. They are very excited to join your project. After a week…
36. JUNIOR DEVELOPER Confessions of a
37. ✤ The code is too hard to understand ✤ Features can't be added that easily ✤ Tests keep breaking all the time for misterious reasons
38. SENIOR DEVELOPER Confessions of a
39. ✤ The code quality is too low ✤ Features can't be added that easily ✤ The test architecture is horrible and needs to be re-written
40. DIFFERENT PEOPLE, DIFFERENT HABITS
41. Ever notice that anyone going slower than you is an idiot, but anyone going faster is a maniac? George Carlin
42. EVERY DEVELOPER HAS HIS OWN STYLE, EXPERIENCE, PRIORITIES AND VALUES
43. MANY OF THESE HABITS COME FROM PERSONAL FLAVOUR, WHICH CAN BE ANNOYING FOR OTHER PEOPLE, BUT NOT NECESSARILY WRONG
44. ON THE OTHER HAND, THERE ARE INTRINSIC & MEASURABLE DEFECTS IN SOFTWARE
45. CODE SMELL High Complexity
46. CODE SMELL Code Duplication
47. CODE SMELL High Churn Rate
48. CODE SMELL Low Test Coverage
49. RAW DATA INVISIBLE PROBLEMS
50. MAKE DATA ACCESSIBLE MAKE PROBLEMS VISIBLE
56. WRAP-UP {
57. WE NEED WORKING SOFTWARE
58. BUT IF YOU ONLY CARE ABOUT WORKING SOFTWARE, YOU LOSE FOCUS ON THE PRODUCT QUALITY
59. WHAT WORKS NOW, MAY NOT WORK TOMORROW
60. MAKE A HABIT OF TRACKING YOUR PROJECTS’ HEALTH
61. USE AUTOMATED HASSLE-FREE TOOLS TO KEEP SMELLS UNDER CONTROL AND MAKE PROBLEMS EVIDENT
62. BUILD A BETTER LEGACY FOR YOUR PROJECTS
63. IMPROVE WORKING SOFTWARE, MAKE BETTER SOFTWARE
64. Ju Liu {Matteo Giaccone @arkh4m @mat_jack1 QUESTION TIME