Mr. Chips, you naughty boy!
filed in Fails on Mar.09, 2010
Submitted through the FAIL Uploader
Game Show Fail
This video is also viewable at: MySpaceTV | DailyMotion | Funny or Die
filed in Fails on Mar.09, 2010
Submitted through the FAIL Uploader
Game Show Fail
This video is also viewable at: MySpaceTV | DailyMotion | Funny or Die
filed in Fails on Mar.09, 2010
filed in Fails on Mar.09, 2010
Soap dispenser fail
Picture by: dunno source Submitted by: UPSgrrrL88 via Fail Uploader
Check out more epic kludges at There I Fixed It!
filed in Fails on Mar.09, 2010

Grinding Fail
I suppose it happens to all of us.
Picture by: dunno source Submitted by: dunno source via Fail Uploader
filed in General on Mar.09, 2010
Excruciating up-to-the-minute coverage of some irrelevant bullshit story that has no ramifications whatsoever.
filed in General on Mar.09, 2010
A couple had been married for 25 years and were celebrating their 60th birthdays, which fell on the same day.
During the celebration a fairy appeared and said that because they had been such a loving couple for all 25 years, she would give them one wish each.
The wife wanted to travel around the world. The [...]
Related posts:
filed in General on Mar.09, 2010
“I was hired as a ‘best practices consultant’ to help bring a 300-developer company’s development practices into the 21st century,” wrote Ian, “and after six months, I had failed.”
“Our first objective was to introduce automated unit testing. They had all sorts of horribly interconnected code, and the tests would help reduce the fix-here/break-there problems. However, after many, many tutorial sessions with developers, and quite a few long meetings spent trying to convince them of the benefits, no tests emerged. The developers stubbornly held that testers should test code, not them.”
Ian continued, “Adding some teeth to our policies, we set-up a continuous integration server that emailed everyone reports of unit test code coverage. This way, managers could take responsibility for getting their teams to write unit tests. That seemed to do the trick: the number of unit tests and code coverage started to steadily climb on all projects.”
“I finally felt that all my efforts were worthwhile,” he added, “the overall health of the team’s code would now increase immeasurably. Less bugs, less time manual testing, and all that good stuff. And then I started to look at the unit test code.”
public class StaticDataRequestTest {
@Test
public void startClientReqest() {
try {
new StaticDataRequest().onData(null);
assertEquals(
" processing client static data request ",
true,
true);
} catch (Exception ex) {
assertEquals(
" processing client static data request ",
true,
true);
}
}
}
Ian added, “I guess we got what we asked for.”
filed in General on Mar.09, 2010
“Ugh, I got iPhone dust all over my giant Dorito.” — CH