teisipäev, märts 23, 2004
Things are the way they are because they got that way... One step at a time.
Fowler, "Refactoring"
Fowler, "Refactoring"
Don't repeat yourself, there sould be one authoritative repository for each concept in a program.
Fowler, "Refactoring"
Fowler, "Refactoring"
As the code gets cleaner, I can see things about the design that I could not see before.
Fowler, "Refactoring"
Fowler, "Refactoring"
Instead of implementing these flexible solutions, ask yourself "How difficult is it going to be to refactor a simple solution into the flexible solution?" If easy, then just implement the simple solution.
Fowler, "Refactoring"
Fowler, "Refactoring"
Flexibility costs.
Fowler, "Refactoring"
Fowler, "Refactoring"
Put things together that change together.
Fowler, "Refactoring"
Fowler, "Refactoring"
Any change to handle a variation should change a single class.
Fowler, "Refactoring"
Fowler, "Refactoring"
Software is meant to be soft.
Fowler, "Refactoring"
Fowler, "Refactoring"
The secret to fast software is to write tunable software first and then to tune it to sufficent speed.
Fowler, "Refactoring"
Fowler, "Refactoring"
Once you have a broad sense of things that refactor easily, you don't even think of flexible solutions.
Fowler, "Refactoring"
Fowler, "Refactoring"
Small methods really work only when you have good names. The length is not an issue. The key is the semantic difference between the method name and body.
Fowler, "Refactoring"
Fowler, "Refactoring"
Writing a test concentrates on the interface rather than implementation (always a good thing). It also means you have a clear point at which you are done coding - when the test works.
Fowler, "Refactoring"
Fowler, "Refactoring"
When you feel the need to write a comment, first try to refactor the code so, that any comment would become superfluous.
Fowler, "Refactoring"
Fowler, "Refactoring"
Tellimine: Postitused [Atom]