EarJava@lemmy.fmhy.ml to Programmer Humor@programming.dev · 1 year agoApproved!lemmy.fmhy.mlimagemessage-square61fedilinkarrow-up11.15Karrow-down119cross-posted to: [email protected]
arrow-up11.13Karrow-down1imageApproved!lemmy.fmhy.mlEarJava@lemmy.fmhy.ml to Programmer Humor@programming.dev · 1 year agomessage-square61fedilinkcross-posted to: [email protected]
minus-squareAsifall@lemmy.worldlinkfedilinkarrow-up2·edit-21 year agoPoor management and time pressure are the answers. It often looks better to push some shit code and then push the fixes later than it does to take twice as long to verify a good change.
Poor management and time pressure are the answers. It often looks better to push some shit code and then push the fixes later than it does to take twice as long to verify a good change.