Stop Thinking in Your "Head"
- 99% of your thoughts are useless.
- "A great many people think they are thinking when they are merely rearranging their prejudices." - William James
- "The greatest weapon against stress is our ability to choose one thought over another." - William James
- You have the ability to decide what you think.
- Your mind should work for you, not against you.
- You can choose NOT to think.
- Which thoughts are useful?
- Thinking about how you can solve problems.
- Understanding knowledge.
- Stop thinking and start feeling.
- How do I train myself to stop thinking useless thoughts?
- Every time you start drifting off, become aware of it.
- Don't judge. Don't think you're stupid. If you do that, you're thinking again.
- THINK STRAIGHT by Darius Foroux - Out November 27
Stop Thinking in Your Brain
One thing I noticed a lot in my work or daily life is that: people (including me) tend to think, a lot. But like this article said, most of our thoughts are just useless. And they are affecting our productivity because of two reasons:
- Our time is limited. If we spend too much time on these useless thoughts, we would have less time on working or thinking the right things.
- A huge parts of these useless thoughts prevent us from doing the real work.
A great example is from an intern I'm mentoring these days:
- In our first-week review meeting, she said that she was afraid that
- her change would break the app badly because she was not familiar with development (Rails, Git, etc.)
- her work (code format, commit messages, etc.) could not meet the company guideline/standard
- her interruptions (asking questions, status updates, etc.) would cause trouble to other team members.
- Due to these thoughts, she didn't take many actions in her first week.
- But from my point of view, these thoughts are useless because:
- If her change breaks the app, we still have Git to recover everything. And she needs more "efforts" to break our codebase on our GitLab server, given that we have branch protection and code reviews.
- If her work doesn't meet the company standards, her mentor would point it out. And as an intern, it's important to make mistakes and learn from them.
- "Projects fail from under-communicating, not over-communicating" (From The Effective Enginner)
Stop Thinking in Your Team
Sometimes, we as a team would make the same mistake as well. If you think of every member of this team as a part of our brain, and the communication between them as the team talking to itself (or thinking in its brain), you'll find that the team also over-thinks, a lot. Here are some examples:
- Adding too many features without talking to the customer.
- Coming up with many edge-cases to make the app "perfect" (bug-free, resilient, performant, etc.).
- Arguing about two different solutions rather than A/B testing them.
Thinking too much as a team would hurt as much, if not more, as a person.
Fortunately, we can use the same solution above to fight that: Awareness.
- Some signs that the team is thinking too much:
- Long meetings/discussions/debates
- No new releases for quite some time
- Polished wireframes that may take weeks/months/years to build
- Every time we discover these signs, we need to become aware of our "thinking" and stop them immediately.
- Start taking real actions and "let the world push you towards more complexities".