Skip to main content

There are no flag days

In life, there are many occasions where the thought of having let down something or someone is so depressing or guilt provoking, that the only way one could counter it is by setting 'flag days'. We decided with solid confidence that from tomorrow onward, we ll do it the other way.The Belief at that point is so re-enforced by one's guilt ridden psyche that we assume it to be a valid solution to the problem. But the issue is, tomorrow never comes.

There is a famous quote that reads:
If you keep doing what you have always done, you ll keep getting what you have always got

At times, we fail to understand the profound fact in the above seemingly obvious statement. The hope that there will be an upcoming change fuels our mind and keeps it going. But are such flag days possible? Is it actually possible to turn one's life with just sheer determination? If so why are there so many rehab centers making their money out of addicts?

Everyone must have experienced the flag day atleast once in his/her life. A day when you promised yourself to change/do something and then ended up not doing it. What is it that introduces this procrastination in a process that we so dearly wanted? Things change. The decision was taken with a completely different set of environmental parameters. The next day it changes, and the old thing may not seem as important as it was.

To solve it, the notion of flag days are to be eliminated. Life flows in a time-space continuum. Life always happens. There are no breaks. So instead of setting flag days, and trying to jump over the hill, start climbing on it, one step at a time. It always works. So the next time you get an epiphany, instead of getting psyched up and jumping you gun, it is much safer to make a proper plan and act upon it - one step at a time.


Post a Comment

Popular posts from this blog


GraphQL What is GraphQL It is a specification laid out by Facebook which proposed an alternative way to query and modify data. Think of it is an as a complimentary of REST/RPC. Now head here and read the  original graphQL documentation . It will take 2-3 hours tops but is a worthy read. This will help you build some impressions on it and help contrast against mine below: Why use GraphQL Core advantage Instead of defining custom backend rpc/rest endpoints for every data-shape, graphql allows you to build a more general endpoint which give frontend/mobile engineers freedom and query and play with the data. It might be less efficient, add a bit more complexity (need for things like  data-loader ), harder to standardize and control client-contracts for. What it looses in complexity and control, it gains in flexibility and freedom - provided your data model is worth of a graphql-ish query  How to tell if my data-model graphql-ish? Are there complex relationships between y

About me

Hi, I'm currently working as a software developer in the logistics industry in San Francisco.  My aim is to impact billions of people's live for the better and make the world a better place. Cheers, Vignesh

Backend - Tech refresher 2019

Hello there As a software engineer, it is important to keep updating your skillsets by learning the latest programming-elements (includes  paradigms,  patterns,  languages,  tools and  frameworks ). This becomes a bit easy if you already working on the cutting edge of something. Even then, it is possible to go too deep and loose breadth. I've taken upon myself to do a tech refresher every year. The intent is to read, experiment and understand these elements by spending anywhere between 4 days to 4 weeks. The ultimate goal is: "do I know most  that I need to know to build a planet-scale backend tech-stack ground up" I'll write up my learnings in posts to help myself (and maybe others) refer it. Here is the initial list I'm thinking about: Redis MySQL, GraphQL Aurora, Mesos, Kubernetes Cadence, SWS Cassandra, MangoDB, NoSQL, MySQL, Spanner, S<, DynDB ELK Flink, Storm, Samza, Spark Hadoop HDFS, Yarn, MapReduce Hive, HBase Kafka, Zookeeper NW: