The curse of knowing how, or; fixing everything (notashelf.dev)

Article summary

The article discusses the curse of knowing how to fix things, particularly in the context of programming and software development. As one gains technical capability, they start to see flaws and inefficiencies everywhere, leading to a sense of responsibility to fix them. This can lead to burnout and an unrealistic expectation of being able to fix everything. The author reflects on their own experiences and the need to learn when to let things stay broken.

Main themes

• the curse of knowing how
• burnout and responsibility
• technical capability and control
• ego and validation
• balance and prioritization
• societal expectations and pressures

What commenters say

• Some commenters agree that the pursuit of fixing everything is a recipe for burnout and that it's essential to learn when to stop.
• Others argue that the desire to fix things is driven by a desire for control and self-soothing, rather than a genuine need to improve things.
• A few commenters suggest that the problem is not just about technical skills, but also about ego and the need for validation and praise.
• Some argue that the curse of knowing how to fix things is not limited to programming, but is a broader societal issue.
• One perspective is that it's okay to abandon projects and not finish everything, as this is a natural part of the learning process.
• Another view is that the responsibility to fix things is not just about personal desire, but also about the impact of one's actions on others, particularly when it comes to creating software that can affect many people.
• There is also a discussion about the importance of balance and prioritization in deciding which problems to tackle and when to let things go.
• Some commenters note that the article resonates with them, but also highlight the need to consider the role of ego and personal motivation in driving the desire to fix things.