Rewrite or Refactor That Is the Question - InitConf 2019
•
1 like•64 views
The presentation from InitConf in Banja Luka (https://initconf.org/)
Recommended
Recommended
More Related Content
Similar to Rewrite or Refactor That Is the Question - InitConf 2019
Similar to Rewrite or Refactor That Is the Question - InitConf 2019 (20)
Recently uploaded
Recently uploaded (20)
Rewrite or Refactor That Is the Question - InitConf 2019
- 1. Vladimir Jovanovic vladimirj.dev Rewrite or Refactor That Is the Question
- 2. PAINFUL TO WORK ON SLOW ONBOARDING BUGS SLOW DEVELOPMENT TODOs
- 3. PAINFUL TO WORK ON SLOW ONBOARDING BUGS SLOW DEVELOPMENT TODOs PAINFUL TO WORK ON SLOW ONBOARDING BUGS SLOW DEVELOPMENT TODOs
- 4. PAINFUL TO WORK ON SLOW ONBOARDING BUGS SLOW DEVELOPMENT TODOs PAINFUL TO WORK ON SLOW ONBOARDING BUGS SLOW DEVELOPMENT TODOs OBJECTIVE-C
- 5. • Founded in 2013 in Germany • It expanded rapidly in the EU market • 2018 – started operating in the US • Provides: • network planning • marketing • pricing • quality management • and customer service to our partner companies
- 6. 5 In 7 figures >7,000 Drivers @partners Countries 30 >2,000 Destinations >350,000 Daily connections Total passengers >100m >300 Network partnersPlatform employees 1,200
- 7. 6
- 9. All startup companies spend their first years creating legacy code. And there is nothing wrong with it.
- 14. REFACTOR REWRITE
- 15. WE ARE THE SAME!
- 16. WE ARE THE SAME! OBJECTIVE-C
- 18. 6 months Feature-freeze Swift Plan 10 months New features in the old app Features cut out Objective-Cadded
- 19. 40+ modules Refactoring … 50% Kotlin Trunk based development
- 20. Rewrite Cons: A lot of planning No new features No direct benefit to the customers Some features are lost It takes longer than expected Huge risk Pros: Greenfield project New technologies Clean codebase
- 21. Refactoring Pros: Constant value Not losing knowledge Lower risk Continuous user testing Cons: Painfully slow Requires careful planning Hard for developers
- 22. The total cost of refactoring is always higher than doing a complete rewrite, but the impact on the organisation is usually much smaller.
- 23. What should YOU do?
- 24. It’s harder to read code than to write it but it’s a bit easier to read it if you had written it.
- 25. I don’t like the code style It uses Framework and not Framework Java Sux! I don’t understand the codebase
- 27. Is the codebase really that bad?
- 28. NO Is the codebase really that bad? YES REFACTOR
- 29. Will there be new features?
- 30. YES Will there be new features? NO REFACTOR
- 31. Do you need more than 6 months?
- 32. YES Do you need more than 6 months? NO REFACTOR
- 33. Can I rewrite the app now?
- 34. Can I rewrite the app now? YES, BUT
- 35. Credits: Articles: • https://www.skcript.com/svr/rewrite-your-app-from-scratch/ • https://dev.to/rhymes/a-big-rewrite-5gl5 • https://daedtech.com/rewrite-or-refactor/ • https://gggritso.com/legacy-code • https://ovid.github.io/articles/a-simple-way-to-fix-legacy-code.html • https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/ Images: • https://www.publicdomainpictures.net/en/view-image.php? image=67199&picture=cooked-fresh-spaghetti • https://emojipedia.org