Troubleshooters vs. Troublepreventers

I just read this about troubleshooters and trouble preventers.

Companies that hire troubleshooters obtain a rapid return on investment, but in the long run they are in more trouble than in the beggining, because troubleshooters think in the short term, so they hire even more troubleshooters. Which means that these companies are not viable in the long run.

Companies that hire trouble preventers do not obtain a rapid ROI, because trouble preventers seem to spend a lot more time getting things right. They also tend to follow strict processes like:

1. Documenting in a wiki.
2. Performing code and design reviews.
3. Running automated unit testing.
4. Performing automated compilation.
5. Running automated functional testing.
6. Performing automated code bug finding using findbugs or PMD.
7. Performing automated code copy and paste detection using CPD.

Optimizing in the short term and in the long term are mutually exclusive. It is impossible to do both at the same time.

How to migrate from one to the other?

Simply work in trouble shooting fixing things trivally in the first time, and then gradually begin increase the amount of planning and bug prevention by introducing design patterns.