Skip to main content

3 Reasons why Overthinking is Good


No, overthinking everything does not make you as smart as Einstein. When have you ever thought about something that was worth overthinking anyway? Overthinking is a serious mental habit that makes us sadder in most cases, or otherwise delusional.

Yet, there are certain advantages to your lifestyle that might make you think you're better off being an overthinker.

You can always see red flags

Since you always think too much about every little weird/adverse/seemingly disrespectful action or word said to you by every person, and especially more so by people close to you, you have a huge advantage over people who are toxic, or are vulnerable to end up with toxic people. Not just qualities like toxicity, but even people who might seemingly end up backstabbing you, cheating on you or just put you down.
Haven't you heard people say, "I don't know why I trusted him/her. The red flags were always there."
It might not be THAT easy to fool you or run you over because you're somebody who looks around on all sides of the road every 5 steps you take.

You analyze relationships, see the changes and can choose to take action

Waking up till 3 am and thinking about how you and your partner or best friend have started drifting apart might not be a reflection of absolute silliness. Sure, sometimes, you might be over-overthinking it. But this frequent analysis of relationships with people closer to you is something that can help a person maintain meaningful relationships. 
And when you do start to see the changes, you can choose to either save the relation, or let it go (if you found red flags).
In fact, one of the major reasons a person overthinks is because they are control freaks. That's why, they think and try to predict.

You can always improve yourself

It's not just about the people and relationships around you. Sometimes, it is about you. If you truly are an overthinker, you will never always blame it on others or even always think about others. Overthinking involves constantly doubting yourself, which upto a certain point, is good. 
It's only when we question our most fundamental values and principles that we truly get the most righteous and correct answers. 
You have explored perspectives, thinking about what a certain person must have thought about you, then questioned if you should be even thinking what others think about you in the first place, and the list goes on. But these series of questions, although mind-tiring, make us realize eventually what we should truly focus on.

You see, we have sessions (not strictly time-based) of overthinking daily where everyday, we think a zillion different thoughts and never ever have we been able to reach a final conclusion, because the thoughts never end. But they do make us realize a lot such as these things above.

So don't be sad or frustrated because you think too much. It's not all bad. 
Limit if it gets to the point where you're interacting less and thinking more. Go out, keep working and on the way home, "overthink".

How do you stop yourself from thinking too much though?

Get it in your head that nobody is more important to you than you. So if anybody is not a part of your life, it won't destroy your's or their life. 
Anything else you say to yourself like 'It's complicated', is just... bleh. I know it probably doesn't make a lot of sense if you have kids, but I'm a 21 year old guy who seems to be really enjoying life following this principle. Once we accept this, we can move on to objectivly see if a person who's being a jerk does deserve to be in our life or not.

So long, fellow Overthinkers!


Popular posts from this blog

Namaste JavaScript Quick Notes

Note:  Akshay Saini's Namaste JavaScript is probably the best course for JavaScript developers out there. These are my personal notes that I made while watching the course; they serve more of as an online quick reference for my understanding and revision, and I hope it benefits anyone reading it too! Everything in JS happens inside an Execution Context. Before a JS code is run, memory is allocated and variables are set as undefined   , and functions are set as their exact code in the scope within the Execution Context. The global execution context hosts all the global variables and function definitions. An Execution Context has 2 components: Memory, that stores variables and functions; and Code, that reads and executes the code. Call Stack maintains the order of execution contexts. Since JS is single threaded and asynchronous, at one point of time, only one function is executed which is at the top of the call stack. For each function, an execution context is created before executi

An introduction to APIs

API is an acronym for Application Programming Interface. Let's start with first defining some basic terms: Browser: These are browsers. To visit any website on the internet, you need a browser. Server: Hmm, this is tough. In simple words, server is a computer. Yes, just like the laptop, or PC at your home. The only difference is that it does not have a screen. Of course, there are other differences in technical specifications, but at its core, the server is just, simply, a computer. That's it. So why is it called a server? Because it serves . When you go to a website like , your computer connects to the internet and gets you your search result. But your computer's internet connection has to get that result from somewhere, right? If the google search result is giving you some answers, the answers have to come from somewhere. What is that place? The answer to that some place is: a server. When you click on the search button on google, or hit enter after typing, &q

Review: Nestjs - Finally a scalable way to build APIs

I have been thinking about this for a long time. There HAS to be a defined way to build APIs in a scalable way.  If you have used Node, Express, etc in your side projects, you might have felt that after a point in development, debugging truly becomes a pain. Sure, enterprise-level API codes are great. But a lot of times, these configurations are too much, and probably not even needed in other projects. To be honest, I haven't seen a lot of Open-Source API codes either to make a judgement on how experienced developers build their APIs. Anyway, I came across an amazing framework recently, and I think if you are coding a complex API, this should be your way to go. Nest.js Nest.js is a framework for building efficient, reliable and scalable server-side applications.  You essentially break your APIs into controllers, services, and modules, which allow you to modularize the smallest of functionalities in your endpoints or the API as a whole. Why is modularizing important? As I have talk