Re:The code culture problem
by chriswarbo on Thursday September 05, 2013 @11:42AM
(#6334829)
Shit code is the third option: Code which was late, over budget and completely unfit for purpose, requiring an army of temp workers to process everything manually while another team come in and spend months on a death march trying to fix it, while the business is hemorrhaging money via lawsuits from pissed off clients with violated contracts.
Is code that was written on time and on budget - but has a few hacks in it shit?
Is code that is beautiful and easily maintainable, but was £1m and six months over budget not shit?