Showing posts from March, 2014

Losing weight is hard

As part of my goal to be in the best shape of my life prior to our wedding, I've vowed to lose all my "Christmas baking" weight before we leave on April 10th.

Our Withings scale shows the damage and poor results so far:

I was very near my goal weight of 160 at the beginning of December, but a month of eating cookies and sweets pushed me to almost 170. This approached the outside limit of a "healthy" BMI.

So for the next 30 days, I'll be following a diet modeled on the Tim Ferriss 4-Hour Body diet (aka "Slow Carb"). It is similar to Atkins and South Beach and encourages high protein intake.

The diet focuses on elimination of sugars and simple carbs that metabolize quickly. I made a chart to post on our fridge to show what we can and cannot eat:

This is a tough diet to follow, but if you stick with it, you're pretty much guaranteed to lose weight, and more importantly, lose fat.

We're combining the diet with the Insanity video fitness progra…

Graphical vs. Text information

Thought of the day: Graphical information takes much longer to produce than text, but is interpreted faster and more accurately.

Software bugs: Focus on what you can control

Developing software is all about writing code and making changes.
Unfortunately, sometimes: 1) the changes affect/break other things in unforeseeable ways 2) the changes are misunderstood and implemented incorrectly 3) the programmer just plain makes a mistake
Nearly all software bugs are a result of one of these 3 causes.
Class 1) bugs are nearly unpreventable and are a function of the software's complexity. This increases with every new feature and custom branch.
Class 2) bugs are 100% preventable. I spend a lot of my time on both ends (clients and developers) trying to clarify and organize communication.
Class 3) bugs are sometimes preventable. This is where we do analysis and prevention, aiming not make the same (or similar) mistake twice.
I work on preventing Class 2) bugs by improving communication and tracking via PMRobot
When a Class 3) mistake is made, we analyze why and determine whether there is a cost effective way to prevent it from happening again.
When Class 1) b…