WebSeitz/wikilog
Buy Build Avoid
Whenever any Form of Government becomes destructive of these ends, it is the Right of the People to alter or to abolish it, and to institute new Government, laying its foundation on such principles and organizing its powers in such form, as to them shall seem most likely to effect their Safety and Happiness.

(backlinks off) (map off)
(search off)
last edited by BillSeitz on Jun 28, 2008 1:20 pm

People typically argue about Buy vs Build.

I bring you a third path: Avoid. The ultimate practice for . to new software!

sing along: "there's no coding, like no coding, like no coding I know..."

In many cases of complex application development, either (a) the process should have been simplified until it could be performed manually, or (b) it should have been eliminated completely, because the inherent complexity would result in a development/maintenance cost which would never deliver an [ROI].

Many companies spent lots of money on a when they probably could have (a) dropped half the features they built which nobody used, then (b) fulfilled the other half of the requirements through a series of manual hacks.

Lots of hacks built by individuals employees, even "departmental techies", don't survive employee [Turn Over].

See : | | | | | | | | | | | | | | | |


 



Bill Seitz, fluxent at gmail dot com, Weblog