Is adding an “if-then” function” the key to hacking weight loss?

October 22, 2016 Ashley 0 Comments

I hate computer coding.

Yet, as a Freshman, I opted to try Java. Just the tip. Just to see how it felt as a major.

Unfortunately, my skill set was tantamount to a scene outta Zoolander.

However, in the midst of my HTML failery, I do recall learning about something called the “if-then” function.

What this function dictated, was that – invariably – if one thing (let’s call it “X”) happened in the program, then that meant another (we’ll call it “Y”) had to happen. No questions. No debate. No “what if I’m too tired when X happens?”. A computer doesn’t suffer from relentless feels and fears sabotaging its long term goals.

So, when X happens, Y has to happen.

Kinda like Tyler’s final rule to be in his underground punch posse.

Now, I’m no Zuckerberg. (Like I said, I suck at coding.) But when I heard about applying this logic to weight loss goals (or any, really), it made a whole lot’ve sense to me. Injecting specificity and realism into goal setting seemed like the missing piece most 5 week, month, or year plans lacked. I can say I wanna lose weight all day long. But if I’m not looking at my life as it is, and deciding how I’m going to build my slenderizing empire day by day, then I’m not taking any steps toward that, am I? The key behind applying an “if-then” function is that it dose a couple’ve things. First, it dictates a specific, reliable “X” will happen that dictates your “Y”. Example? “As soon as it’s 7 A.M. (thing X), then I’ll lace up my Asics and hit the gym (thing Y).” No arguing. No debating when to work out. That’s just a thing that happens at 7 A.M. now. 7 A.M. is sure to happen, so you’re sure to have that X catalyst to kickstart day 1 of your goal achievement.

The second bit’ve this?

Being realistic about your “if-then” by adding a backup “if-then” function to fitness coding.

And part’ve being realistic is owning your defects and tendencies. For example, if you’re like me, you have a whole compendium of excuses at the ready to avoid doing shiz you don’t wanna do. Among my faves are “I’m too tired”, “It’s too cold outside”, and “I’m too tired”. The trick with the second element of your if-then-ery is to hack this as well. Be proactive. Outline those excuse defects ahead of time, and have a new X/Y combo at the ready. “If I’m tired to workout (X), I just get decked out in my sweat threads and get in my car (Y).” (’cause sometimes convincing yourself to do the lesser thing is easier – and by the time you’re dressed and out the door, you’re more capable of telling yourself “might as well”). This is superior to just assuming you’ll be willing to wake up and hit the bricks because it allows you to get honest with yourself. What excuses are you capable of coming up with when the alarm goes off? What X’s can you “X” out before they have a chance to attack your weight loss goals? Play around with it ’til you find something that works. If you’re too tired (X), then maybe you definitely work out after coffee (Y). If you’re not in the mood for cardio after work (X), then maybe you do strength training instead (Y). If you don’t have time for a long workout (X), then maybe you do an HIIT sesh (Y). When it comes to hacking your binary body, the possibilities and permutations are endless.

So, that’s it.

Wait for that consistent X to happen, and then do Y – without asking “why?”.

(Or turn that “why” – beforehand – into yet another X that’ll cancel it out.)

And “if” you code that into your corporeal computer….

… “then” its proportions’ll go from old school IBM to tiny notebook in n0 t1me.