EarJava@lemmy.fmhy.ml to Programmer Humor@programming.dev · 1 year agoApproved!lemmy.fmhy.mlimagemessage-square61fedilinkarrow-up11.16Karrow-down119cross-posted to: hdev@lemmy.world
arrow-up11.14Karrow-down1imageApproved!lemmy.fmhy.mlEarJava@lemmy.fmhy.ml to Programmer Humor@programming.dev · 1 year agomessage-square61fedilinkcross-posted to: hdev@lemmy.world
minus-squareAsifall@lemmy.worldlinkfedilinkarrow-up1·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.