Write a draft or "monolith" first
Refine/refactor it
Think
Code
Think again
Optimize/refactor
Refactor first, write code after that
Change the "pseudo code" first, the real code after that
Refactor to isolate changed part
Refactoring is good, technical debt is bad
Refactoring is a mandatory part of the iterative development
Continuously refactor unclean code to clean code
Always refactor for changes in the requirements - "Until now the program had to do this, from now on the program has to do that"
(Not part of this training. See links.)
Last updated 5 years ago