If condition

If condition is a popular concept in most programming language. It’s a convenient way to define our reaction based on a certain situation. For example, I want X to be executed if Y situation occur.

However, I’d like to think that it’s a common analytical framework that we also use a lot in our day to day life. Like how we promised ourselves that we’re going to change if a particular situation occured.

I use it a lot too, especially last year. Like, how I think that I would start to work on my book if I move out to Bali. Or, how I think I would take a yoga class if I stay in Ubud.

But now that I move back to my hometown, I don’t have the luxury of doing such an extreme if condition anymore. It means that I need to set a more realistic if condition if I want to maintain my current lifestyle.

I understand it’s a gradual change. I used to live in big cities for the past 7 years. Having to cut myself from the big-city life is as terrifying as the first time I move there. Hence, adjusting my mindset is as important as adjusting my communication style. I realize that the “ifs” need to be more modest now.

The “if” is the trigger. And once we set the trigger, we create dependecy. We link an action into another action. So we need to be careful not to over-complicate our life because of these dependencies that we set.

And indeed, if we’re talking about changes, the “if” needs to be as make sense as possible. Otherwise, the “if” that we set will never happen and even turned into a blocker. And sometimes, maybe we don’t even need the “if” in the first place. Maybe we should just say “I’ll do my best, no matter what. And I will let God define the result. No condition, whatsoever.”

This essay was originally published in the first edition of my newsletter.