Skip to main content

When I will be King : Solution to New Year Resolutions

Many a times I have felt, and most of you might also have felt, what would you do if things went the way you want. Sadly, we cannot get the world run the way we wish, but we can definitely put all those sweet and crazy thoughts in words. So here I present, "When I will be king" series in which I will post all those fetishes I would accomplish when I will be king.
The original idea comes from a very geeky blog that I read sometime during November last year and thought of having something similar on my blog as well. It happened to be my New Year Resolution. Two months passed and I hardly got time to log into the blog. Better late than never. Right?
So here I go.

Opening Post (from that same geeky blog.)
When I will be king

I resolve to end New Years resolutions.
Every year, we're supposed to make resolutions for New Years. Things we want to accomplish. Personal Goals. New healthy habits. Things to strive for.

You know what resolutions are? They're a setup for defeat.

If you bother to make any resolution at all, you try for something lofty; you set some goals that sound nice:
“I'm going to go to the gym 5 days a week”
"I'm going to lose 10 kgs”

Of course, the result is that you fail to achieve the goals. Why change things now? You've lived this long, why put yourself out on the whim of the calendar turning over to the new year?

So another resolution dies an early and hushed-up death. The year crawls by and another New Years comes up and you make another attempt:
“I'm going to hit the gym 4 days a week”
“I'm going to lose 5 kgs”

On it goes, year in and year out: we set goals, we blow them, we feel awful about ourselves.

Why do we need this stress? What's the point in creating a game that we're bound to lose?

My administration will impose something new and exciting called:

Presolutions

With this new twist on the old tradition, people will look back on the previous year, pick something they are proud of, or just something that happened to them, and set a goal that they will have achieved already:
“I will have avoided setting one foot in the gym all year.”
“I will have gained 20 kgs”

No longer will we fail to attain goals; we will succeed every single year, by definition.

Why be Future Failures? Let us be Past Achievers instead.

Presolution: the Resolution Solution.

Comments

Popular posts from this blog

The economics of crypto investing

If you believe in the greater fool theory, there is no other market as speculative and volatile as the crypto market today. We are perhaps living in the biggest bubble of our times. I am not bullish on this market in particular. I am bullish on the mania. 90% of the cryptos we see today will crash. They are just tokens with no tangible value generation capability. However, I believe that the mania and euphoria will stay.

Having said that, should one consider investing in this market? Certainly!
The risk/reward is lovely, potential upsides and margins are huge and with 3-5% of your net worth, the bet on the mania is worth it.

How does one choose where to invest?

If you follow the stock markets, you are expected to do thorough Fundamental Analysis before investing. Expect the same for the crypto market. I invest in large caps. I invest in index funds. And I invest over and over again. Markets rise, always. Extrapolating the same strategy - invest in indices - the top 10 tokens by perfo…

Learn frontend to get good at backend : lessons for my 20 year old self

Only when you are the consumers of your own products, can you design the best ones! Same philosophies go for API design and programming in general.

This advice may seem counter-intuitive at first, but trust me, the best way to get better at backend programming is to spend some time doing frontend! It will teach you a lot about how your APIs are being used in the "real world". A first-hand experience of API consumption will tell you a lot about your design philosophies!

Capture and compare stdout in python unit tests

A recent fan of TDD, I set out to write tests for whatever comes my way. And there was one feature where the code would print messages to the console. Now - I had tests written for the API but I could not get my head around ways to capture these messages in my unittests.
After some searching and some stroke of genius, here's how I accomplished capturing stdout.