The systematic practice of
to achieve one's objectives with a code base, without stopping to so much as
, let alone
This phenomenon has several common causes, but they are all usually rooted in the culture and process TheManagement
choose to promote.
Constant pressure to JustMakeItWork
and then ForgetIt
: essentially untempered
doesn't sell the product, therefore it has net negative
because people spend time improving it.
A shortage of people with both
and familiarity with enough of the system. This can be due to too many people that
, hiring too many junior people because they're cheap headcount, or someone playing
Insufficient resources devoted to testing, whether
s or even plain old
. Typically there are only enough resources allocated for a single round of
just before the software ships.
One of the most damaging types of
is expedient coupling of different parts of the system -- enough of this and eventually the modularization succumbs to the
and you're left with a
View edit of
November 10, 2014
with title or text search