I divided by two... damnit!

[Fenixgoon]

So for work I'm designing a test fixture to test materials (ie, break stuff in a controlled way) and I stupidly divided by two when doing some math. In revising some of my work today, a couple of weeks after the initial design, I realized I needed to double the load carried by the fixture (and slightly then some due to another mistake).

I hate when I make dumbass mistakes :| :| :|

At least I realized it before I had our machinist make a prototype frame and before we ordered tons of materials (big $$$$). That would have been a disaster.

 

[apac]

Measure twice, cut once. GJ finding it.

 

[coldmeat]

Everybody knows you never divide by two.

 

[Jeff7]

Yeah, the stupid mistakes are the most fun.

Quick, what's 3²!


Damn, it's not 6.
And I will sometimes magically turn x² into x, pretty much for no reason.
I'm sure that in 200 years, they'll discover that this was somehow the key to the Grand Unified Theory, but I doubt that'll get me very far today.

 

[FoBoT]

Originally posted by: coldmeat
Everybody knows you never divide by two.

at least he didn't divide by zero
http://pics.bbzzdd.com/users/J...rek_divide_by_zero.gif

 

[duragezic]

A while ago I was working on an app for the Sun SPOT and I needed to check if some accelerometer values were within a specified tolerance. i.e.

if (value >= value+TOL || value <= value-TOL)


That piece was part of more new code I added to try a new idea that I thought was going to work great. I fired it up and it was full of fail. I ripped up my code wondering why it was not working much at all. I kept redoing parts but kept copying the above lines thinking that obviously something as trivial as my "isInRange()" piece worked.

When I did finally realize the error and fixed it, my original idea did end up working pretty well. Still, that was one of my more bonehead mistakes!

 

[Suspicious-Teach8788]

safety factor of 2 at least...