Surviving and working efficiently with legacy codes is becoming more and more of a nightmare for long running projects, big companies and young engineers. It’s becoming a norm in software development - thus modernizing and reimplementing them is deemed highly necessary. In this session let's take a deep look into how legacy codes are made and how we can safely refactor/reimplement them.
Introducing Microsoft’s new Enterprise Work Management (EWM) Solution
Make legacy code great
1. München/HQ Bamberg Berlin Đà Nẵng Dresden Grenoble Hamburg Cologne Leipzig Nuremberg Prague Washington Zug
Make Legacy Code Great Again
Ezekiel Olasehinde
Đà Nẵng, 11/07/2020
Why should you trust what I say,
2+ years of working with the greatest legacy code
8+ month rewriing/rewriting and implementing configurable components for the project
Unspupported technology Java 1 to 14
You code is not documented, it’s difficult to understand how the code is supposed to work
Unsupported technology
Not tested
Inherited
find a good question : how much legacy code do you think you've made
- Explain how you're forced to create legacy code : my resolution
Technical is usually created due to time pressure, we can call them ”The Little Hack”
1. Example : how I was forced to create a technical debt
Technical debt is similar to Monetary debt in the sense that they accumulates until fulfilled
Technical debt and legacy code as whole leads to refactoring
Transition: how do we ensure were refactoring correctly ?
Expected demo time: ~ 5 - 6 mins?
Too much information – make sure the pointers are connected to things said in the speech – need more information
How many take-aways can one personally remember? Choose the most important