Unmaintainable code, repetitive bugs, time-consuming corrections, depressed teams ... No wonder most of us prefer to start projects from scratch (a.k.a. Greenfield) rather than a Legacy code base (Brownfield). For sure, situations where control has been lost are annoying, even more: exhausting. But what if we were wrong? What if -fully equipped with some refactoring techniques and communication skills- we were able to reverse things and get back control over such situations? During a session with real live-coding inside, come and discover the tips and tricks from people who prefer to regain control rather than undergo. From people who prefers the hidden opportunities of the legacy to the blank pages of the Greenfield projects. You too, realize it could be fun and join the Legacy Club!

1. Legacy ClubTake back the control – Never give up

2. Thomas PIERRAIN @tpierrain
BRUNO BOUCARD @brunoboucard
founding members

3. A sad state…

4. understanding sometimes…

5. Nay WTF…

6. Rushing, always rushing …

7. After a while …

8. You get this …

9. And A huge bill

10. a mess at every level…

11. What if we succeed collectively…

12. So tell us,
Where does our
legacy come from?

13. Legacy?
It's the others!

14. legacy?
It's our industry's
fault…

15. Legacy?
It's a curse!

16. Seriously…
Where does Our legacy come
from?

17. You still don't
see it, right?

19. Legacy is when …

20. IT’s when…

21. legacy
is all of us

22. The legacy
It’s the code
+ US all

23. The code + US ALL

24. « Software is eating the world »
Thus, It’s time for us…

25. … to change

26. Are YOU READY?

27. ChapTER1communication & culture

28. we are social animals…

29. So …
Why are we going
around in circles?

30. …
We have lost our way
We have lost our motivation

31. plus …
Lack of communication ;-(

32. Without feedback
we are off the radar

33. The Wake up
First step?

34. Restore a relationship with the business

35. Our First job as a developer?
“Understand the domain
we’ll have to code”
( Jérémie GRODZISKI )

36. Put yourself in their shoes…
em-pa-thy
noun ’em-pe-thé
the feeling that you understand and share
another person's experiences and
emotions : the ability to share someone
else's feelings.

37. they don’t want to collaborate?
Secret Weapon:

38. event storming To the rescue

39. THE Most
important is
To HAVE GOOD
conversations

40. Culture
StratEgies
Warning: if we ignore the culture…

41. It comes back to…

42. A TIPS
no man is a prophet in his
own land

43. To change the culture of a team,
start at lunch-time

44. Starting with ourselves
Stay curious, practice,
Help others

45. Egoless Programming
1. You are not your code
2. No matter how much “karate” you know, someone
else will always know more
3. The only constant in the world is change
Be open to it and accept it with a smile
4. Don’t be “the coder in the corner
5. Be kind to the coder, not to the code
6. Don’t rewrite code without consultation
7. …

46. Software Craftsmanship?
It’s a mindset!
Passion
Discipline
Motivation
TRANSMISSION
Efficiency

47. A continuous improvement
Observation
Improvement

48. « Yes but, here It's impossible to
take back the control! »

50. Can’t take back the control?
« Resolve to serve
no more, and you
are at once freed »
(La boetie)

51. Chapter 2Freedom through mastery

52. Foster a curiosity for the domain

53. To avoid temptation
(When we feel rejected)
Confort-zone
( Tech only )

54. Already met an expert beginner?

55. Go back to basics
Master your tools

56. Practice, practice, practice…

57. Would you dare?

58. We’d rather get
ready!

59. Test harness

60. But also...

61. Know your enemies

62. Code Smells
Name your enemies
Long method
Large class
Long parameter list
Primitive obsession
Data clumps
Feature Envy
Inappropriate IntimacyMessage Chains
Divergent Change
Shotgun Surgery
Parallel Inheritance
Hierarchies
Switch
statements
Temporary field
Bad naming
Dead Code
Speculative Generality
Duplicate Code
Alternative classes with
different interfaces
Refused bequest
Conditional
Complexity
Indecent
Exposure

63. Live-coding Code smells

64. ChapTER 3Hard-core refactoring

65. Attack on the legacy…

66. Where do we start?

67. Business value first!

68. « my code is untestable! »

70. Test or the Egg?
We want to add more
tests to our code
We have to
refactor our code
to be testable
We can't refactor
without tests

71. Until you didn't set up a test
harness, brace yourself!
Hyperaware
Editing
Never change public
contractsa single goal at a time
Pair / MOB
Programming
Delegate to the
compiler

72. But there are a few
techniques…

73. To break your dependencies
Parametrized Method
Introduce Instance
Delegator
Introduce Static Setter
Parametrized
Constructor
Extract Interface
Extract &
Override Call
Adapter Parameter

74. Live-coding Breaking dependencies

75. And what if we are really in deep…

76. You can either start again
from scratch…
#Green-Field

77. Or stop believing in...

78. # legacy? It's all of us!
# Focus on business - get a sense
# Practice before leaping
Take back the control – Never give up

79. Join the legacy club
Take back the control – Never give up

80. Thanks!

81. Questions?

82. Legacy ClubTake back the control – Never give up