DEV Community πŸ‘©β€πŸ’»πŸ‘¨β€πŸ’»

Aseem Bansal
Aseem Bansal

Posted on • Updated on

Do this when confused about what to spend your time on

There are days when we get confused by having too many choices. Confused about what we should learn. Because there are so many choices.

I recently came across a story which helped me clear my thoughts on this topic.

There once was a donkey. The donkey was hungry as well as thirsty. On one side there was water and on the other side there was food. The donkey kept on thinking which side to go first. At the end the donkey did not move and died.

What's the moral of the story?

Do not fall in the trap of short-term thinking. Think long term and plan long term.

I am currently 27 years old. There is a lot left to live. I like this website https://www.failflow.com/die/1450. It shows me exactly how much assuming average life expectancy.

I am on week 1,451 of 4,732 of my life.
If it takes 50 weeks to become advanced at any skill, I can learn about 44 new skills during my career. 64 if I include retirement.

We live in the age of instant gratifications and our attention spans have shortened. This has led to us thinking short term. Instead of planning for a few years we plan as we are going to die next week.

There would always be a need to balance short term and long term efforts. But we should not get confused between what is for short term and what is for long term.


If you want to know when I write more articles join telegram channel for Data posts, software posts or other posts. I don't spam,Β promise.

Top comments (2)

Collapse
 
ratcat profile image
RatCat

Very fantastic talk. That's the situation i am spending. Hope i will get back to trac again.

Collapse
 
anshbansal profile image
Aseem Bansal

I hope you do. Best luck with that.

Timeless DEV post...

How to write a kickass README

Arguably the single most important piece of documentation for any open source project is the README. A good README not only informs people what the project does and who it is for but also how they use and contribute to it.

If you write a README without sufficient explanation of what your project does or how people can use it then it pretty much defeats the purpose of being open source as other developers are less likely to engage with or contribute towards it.