Code refactoring
Description:
From proof of concept to clean code. We do iterations of the code during developement, we try to catch the term. But then we often produce not readable or optimal solution. For this and many other reasons we try to make our result be as good as possible. Refactoring is the way to this goal.
Links:
https://en.wikipedia.org/wiki/Code_refactoring
Keywords:
clean readable code maintanance
Motivation:
make it bullet-proof
Requirements/Prerequisities:
algorithmisation, optimalisation, performance
Level:
concret: specific best practice (e.g. use microservice)
Application domain:
Software engineering
Main phase:
Development: Implementation/Code/Build
Related literature:
Wake, William C. (2003). Refactoring Workbook. Addison-Wesley. ISBN 978-0-321-10929-3.
In which projects do/did you use this practice?
SIMUportfolio
Software Engineer
>10 years of experiences
Masaryk University
1. How do you rate the potential benefit for your projects? | 4 |
2. How often are you using that practice? | 4 |
3. What is the effort to introduce the practice in your project upfront? | 4 |
4. What is the effort to apply the best practice in your project daily basis? | 4 |
Questions 1, 3 and 4 (1 = Low, 5 = High)
Question 2 (1 = Never, 5 = Always)