Maximum effort, minimum code

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." -- Antoine de Saint-Exupery
Some time ago I worked on a project with a development lead who believed the answer to every problem was a framework, a meta-data layer, another integration pattern, another implementation of MVC and so on...

While that sort of "enterprise" solution development is commendable in certain scenarios it's often over engineered. After a lot of coaching he managed to overcome his default setting of "maximum effort, maximum code" and while never reaching comfort with F.I.A.T* a happy compromise was reached.

In summary, the perception that a problem is a technology problem is often misplaced.  Instead, look at the people and the process to spot the real issues...

And since it's Friday, a nice segue to someone else who loves "maximum effort"...



*=Fix it again tomorrow.  The default devops pattern in some proprietary trading firms and hedge funds...

Comments