The author mentions a few things which really made me remember some of my old colleagues. Especially this part:
They indulge in voodoo debuggingBad programmers will often shoot from the hip about why certain issues are happening, without proper disciplined investigation into surgically identifying what is going wrong. They will blame other people's code, 3rd party libraries, hardware and what not else without actually pinpointing issues.
Their coding algorithm is:
while (1) { change_something(); if (whatever you changed works) { break; }}
Rather than the one pass:
do_something_right();
