I'm implementing simple damping code in my self-balancing skateboard code and I was looking at the result data and something didn't look quite right. Here is the source before I caught it GyroData returnData = (GyroData)dampenData[0].Clone(); // was new GyroData(); int length = dampenData.Length; // only values we really care about damping for (int i = 0; i < length; i++) { returnData.Pitch += dampenData[i].Pitch; returnData.Yaw += dampenData[i].Yaw; returnData.Roll += dampenData[i].Roll; returnData.TiltX += dampenData[i].TiltX; returnData.TiltY += dampenData[i].TiltY; returnData.TiltZ += dampenData[i].TiltZ; } Anyone catch it? I didn't either...

So I have a few things going on right now: Peace Love Code post for Coding4Fun A SMS blaster for Windows Mobile to cause some trouble with American Idol since I hate the show that much (will be on Coding4Fun) A Facebook / Twitter mash-up application (will be on Coding4Fun) An unnamed Twitter application that will be pretty sweet (will be on Coding4Fun) Another project I can't say since I think Dan will kill me. Skateboard Segway for Maker Faire (will be on Coding4Fun) Bartender Version 2 (will be on Coding4Fun) Channel 8 Videos (some may be on Coding4Fun)...

So my father and I are distinctly two different styles of engineers.  This was made clear when we were building the frame for my skateboard segway.  This XKCD strip outlines partly why this may come up: So my dad is mechanical and I'm a computer engineer.  I was heavily afraid of not getting the frame done in time while he was afraid I wouldn't get the software written in time.  I'm freaking out since I don't think the hardware will be done and he is freaking out cause he is under the impression my lazy ass...

Here is the frame almost done.  The motors actually had to be removed due to a little issue but this is a near finished version.  I've decided to move everything possible to under the skateboard.  Why would I move the eBox 2300, gyro, and speed controller under?  So I can have 10.8 Amp Hours worth of NiMH batteries hidden and a full charger in the frame.

I'm a very special child when it comes to the English language.  Andy pointed out something everyone already knows, I suck at spelling.  Varient should be spelled Variant.  Good thing Visual Studio has find and replace for the Code Portfolio program.  Good thing all you need to do is rename the file and Visual Studio fixes all your references and renames the class automatically.