Ennis Ray Lynch, Jr. wrote:
what I can't live with is developers that don't test any code they right
I'm assuming you mean "write", not "right". If they are copy/pasting, did they write anything? (Reminds me of "If a tree falls in a forest...") Unfortunately, I see code get promoted all the time that won't work correctly. Which means it wasn't tested by the coder in the first place. Then again, sometimes I'm guilty. I needed to have something run 5 minutes before midnight, so I coded the job to run 5 minutes before midnight. Worked like a charm, truncated tomorrow's table every time. One minor detail, code is running UTC time, job uses local time. Tester finds the bug the day before I leave. I don't have time to fix. A year later, I'm in a different group, but my former group asks us to review code changes. All the jobs are being routed to a different service center with a different time zone. They come up with a neat idea. Set up these jobs to be scheduled based on UTC time and figure the offset of local time to UTC and set the local time to the desired UTC time. To my horror, this job is scheduled to run at 7:55AM UTC. I tell the team about the original bug and they need to either set the time to 11:55PM UTC time and require the job is rescheduled every time the time changes or run at 10:55PM UTC and accept the job will either be on time or 1 to 2 hours earlier than the desired time. Right now (back then) it is running 16 to 17 hours earlier than the time it should. Even when copy/paste isn't directly used, it sometimes pops up in code.
