The 5 People in your Organization that grow Legacy Code
7 likes8,466 views
The presentation by Roberto Cortez discusses the nature of legacy code and the importance of understanding different developer profiles in managing it. He identifies five types of developers—overly energetic engineers, technology enthusiasts, firefighters, smartasses, and interns—each with unique traits and approaches to work. The key to effective collaboration is to recognize and accommodate these differences to enhance team productivity and code quality.
![public static int getTokenCounter(String[] tokens) {
int j = 0;
if (tokens.length >= 5) {
j = 5;
}
else if (tokens.length == 4) {
j = 4;
}
else if (tokens.length == 3) {
j = 3;
}
else if (tokens.length == 2) {
j = 2;
}
else if (tokens.length == 1) {
j = 1;
}
return j;
}](https://image.slidesharecdn.com/con4255the5peopleinyourorganizationthatgrowlegacycode-141002180144-phpapp01/85/The-5-People-in-your-Organization-that-grow-Legacy-Code-9-320.jpg)
The 5 People in your Organization that grow Legacy Code
- 1. ! The 5 people in your Organization that grow Legacy Code Roberto Cortez JavaOne 2014 #CON4255
- 2. Roberto Cortez Freelancer, Speaker, RebelLabs Author, Blogger, Passionate Developer twitter: @radcortez ! mail: [email protected] ! blog: http://www.radcortez.com
- 3. This presentation is NOT about •Testing •Tools • Refactoring • Or any other thing that you heard before (hopefully)!
- 4. It’s about • Knowing yourself • Knowing others • Dealing with each other differences
- 5. “In historical terms, a legacy is something that is handed down from one period of time to another period of time.” (from Wikipedia) What is Legacy?
- 7. What is Legacy Code? • Is it old code? • Is it code no one wants to use? • Or is just badly written code?
- 8. public static String getDayOfWeek(String data) { switch (getDOWNum(data)) { case 1: return "Monday"; case 2: return "Tuesday"; case 3: return "Wednesday"; case 4: return "Thursday"; case 5: return "Friday"; case 6: return "Saturday"; case 7: return "Sunday"; } return ("???"); }
- 9. public static int getTokenCounter(String[] tokens) { int j = 0; if (tokens.length >= 5) { j = 5; } else if (tokens.length == 4) { j = 4; } else if (tokens.length == 3) { j = 3; } else if (tokens.length == 2) { j = 2; } else if (tokens.length == 1) { j = 1; } return j; }
- 11. Legacy Code is •Unknown •Scary •Ignored
- 12. Legacy Code is everywhere • Huge investments in software are to solve business problems, not code problems •Technology evolves way faster than software •New frameworks are released every year
- 14. Identify the Source! • Code is written by developers •Tools can help, but they are not enough • Developers are the main contributors!
- 15. The Overly Energetic Engineer ! The Technology Enthusiast ! The Firefighter ! The Smartass ! The Intern
- 16. The Overly Energetic Engineer
- 17. The Overly Energetic Engineer •Perfectionist • High standard for Quality • Ask a lot of questions •Focus on key details •Very critical • Study a lot
- 19. The Technology Enthusiast •Very enthusiast about their work • Friendly and open • Speak a lot • Optimist •Wish to be recognised by their skills
- 20. The Firefighter
- 21. The Firefighter • Enjoy helping others • Like to work in teams •Patient • Calm people in stressful situations • Investigate facts
- 22. The Smartass
- 23. The Smartass •Focus on instant results • Demands from others •Impatient • Like to accept challenges •Impose their rules • Lead other people
- 24. The Intern
- 25. The Intern • Developers starting their own career • It’s a temporary stage • They need to learn
- 27. Golden Rule? “Treat others the way you want to be treated!” WRONG!
- 28. Golden Rule! •Everyone is different! •Everyone have different needs! • Psychology is tied with everything we do •Learn how to handle each profile
- 30. The Overly Energetic Engineer • Delegate them important tasks • Give them opportunities to show their skills • Provide freedom to explore • Assign investigation work
- 31. The Technology Enthusiast • Don’t let them rearchitect • Clarify how things should be done • Research facts for the problems •Need to be included in decision making
- 32. The Firefighter •You shouldn’t pressure them • They need to feel confidence • Provide them with accurate information • They may need a step-by-step plan to proceed
- 33. The Smartass •Have all relevant information with you • Provide them with end solutions • Present alternatives • Give them facts and direct answers
- 34. You have the tools!
- 35. Remarks •People are not exclusive to one profile • They can adopt any behaviour or even a combination •Usually, one profile more predominant
- 36. Proof? ! Empirical Data!
- 37. Inspiration •Heavily inspired in DISC •Behaviour assessment tool • Dominance, Influence, Steadiness, Conscientiousness
- 38. Wait! The Intern? • Invest • Promote peer code reviews • Quick presentations about technology •Teach them!
- 39. Last Words!
- 40. Golden Rule? You can drive people’s behaviour by learning how to accommodate each person unique characteristics!
- 41. Questions?
- 42. Thank you for Attending! twitter: @radcortez ! mail: [email protected] ! blog: http://www.radcortez.com