I read Bram's resume and wondered what he meant by proces. Waterfall methodology? What is that? 30 seconds later and a couple of cycles more spent at the google search-engine farm I got the answer:
It turns out that it is the methodology they try to teach us at the university. 4 phases: Analysis, Design, Implementation and Test. But of course it doesnt work. Evolutionary design in which you continously repeat the above 4 phases each time reaching another milestone in the project where hopefully more and more works is far better in my opninion.
The reason is simple: Every project has errors. If they come at the analysis phase in the waterfall methodology your next 3 phases are doomed. On the other hand a review in the evolutionary process should hopefully result in the problem being exposed
No method is totally error-free though. Such is life. So you still have to do the basics:
Think! Strategy before tactics. At some point it is important to stop thinking though. Detailing everything beyond measure is probably just a silly waste of time.
Divide! Smaller problems are easier to solve than big ones. When they accumulate they will eventually solve the big problem.
Use modularity. Reuseability is mostly a dead fish but inside a given project the reuseability can be quite high, so use it.
Measure! There is no reason to turn on the performance knobs when you dont know where it hurts. Remember the cache of newer systems. It often plays more than a major role.
Understand! Errors should never be solved by turning on the semantical knobs of the program. Understand why it fails and then do the fix correctly.