Your last point about fixing things and cleaning it up (refactoring?) becomes easy and possible if good engineering practices were followed in the first place. Repeating the same mistakes again and increasing your workload is not very smart.
On 12/3/10, Kenneth Gonsalves <law...@au-kbc.org> wrote: > On Fri, 2010-12-03 at 15:34 +0530, steve wrote: >> Most good engineering practices get thrown out of the window under >> pressure. > > this is the real world. Monkey patching, hacks, repeating the same code > in 10 different places with minor changes - all this and more happens > when the deadline is yesterday and the client is screaming and tearing > out his hair. The other day a developer produced some code in production > which did only half the job. Reason? He did not want to violate the DRY > principle! Customer does not give an rf about DRY - he wants results and > correct results in production. After all the hue and cry dies down, it > makes good sense to go back to the code and slowly remove all the > repetitive parts, make the hacks look good and redo the monkey patching > - if you have time. > -- > regards > Kenneth Gonsalves > > _______________________________________________ > BangPypers mailing list > BangPypers@python.org > http://mail.python.org/mailman/listinfo/bangpypers > -- ~noufal http://nibrahim.net.in _______________________________________________ BangPypers mailing list BangPypers@python.org http://mail.python.org/mailman/listinfo/bangpypers
