The blog post "The curse of knowing how, or; fixing everything" explores the burden of expertise. Highly skilled individuals, particularly in technical fields, often feel compelled to fix every perceived problem they encounter, even in domains outside their expertise. This compulsion stems from a deep understanding of how things should work, making deviations frustrating. While this drive can be beneficial in professional settings, it can negatively impact personal relationships and lead to burnout. The author suggests consciously choosing when to apply this "fixing" tendency and practicing acceptance of imperfections, recognizing that not every problem requires a solution, especially outside of one's area of expertise.
The author of "The curse of knowing how, or; fixing everything" explores the burdensome phenomenon of possessing extensive technical knowledge, particularly in the realm of software development. They elaborate upon the psychological and social ramifications of being the designated "fixer" within their personal and professional circles. This predicament arises from a deep understanding of how systems function, enabling them to diagnose and rectify issues that others struggle to comprehend, let alone resolve.
The post details how this constant demand for troubleshooting can become a double-edged sword. On one hand, the author derives a sense of satisfaction and validation from their ability to assist others and overcome technical challenges. This proficiency allows them to streamline processes, improve efficiency, and generally make things work better. It fosters a sense of competence and control, a comforting familiarity within the complex world of technology.
However, this expertise comes at a cost. The author describes a sense of obligation, a feeling of being perpetually on call to address technical malfunctions, whether large or small. This expectation can lead to exhaustion and resentment, particularly when the requests become excessive or impinge upon their personal time. They elucidate the frustration of witnessing inefficient practices or easily avoidable mistakes, knowing they possess the knowledge to prevent such issues, yet often lacking the authority or opportunity to intervene proactively.
Furthermore, the post touches upon the difficulty of relinquishing control and allowing others to learn through their own struggles. The author recognizes the pedagogical value of independent problem-solving and acknowledges that their constant intervention can stifle the development of others. However, the impulse to immediately rectify problems, driven by a desire to optimize and improve, often overrides this awareness. This internal conflict creates a tension between the desire to help and the understanding that sometimes, the best assistance is to allow others to grapple with challenges independently. The author concludes by reflecting upon this dilemma, acknowledging the complex interplay between their technical expertise, their desire to assist, and the necessity of allowing others to develop their own problem-solving skills. They express a desire to find a balance between offering support and fostering independence, ultimately aiming to mitigate the "curse of knowing how."
Summary of Comments ( 286 )
https://news.ycombinator.com/item?id=43902212
Hacker News users generally agreed with the premise of the article, sharing their own experiences with the "curse of knowing." Several commenters highlighted the difficulty of delegating tasks when you know how to do them quickly yourself, leading to burnout and frustration. Others discussed the challenge of accepting imperfect solutions from others, even if they're "good enough." The struggle to balance efficiency with mentorship and the importance of clear communication to bridge the knowledge gap were also recurring themes. Some users pointed out that this "curse" is a sign of expertise and valuable to organizations, but needs careful management. The idea of "selective ignorance," intentionally choosing not to learn certain things to avoid this burden, was also discussed, though met with some skepticism. Finally, some commenters argued that this phenomenon isn't necessarily a curse, but rather a natural consequence of skill development and a manageable challenge.
The Hacker News post titled "The curse of knowing how, or; fixing everything" (linking to notashelf.dev/posts/curse-of-knowing) generated a moderate amount of discussion with a variety of perspectives on the core issue presented in the article: experienced developers feeling compelled to constantly "fix" things, even when it's not their responsibility or the optimal use of their time.
Several commenters resonated strongly with the article's premise. One user described the experience of joining a new company and feeling overwhelmed by the number of things that "needed" fixing, leading to burnout and frustration. This commenter highlighted the tension between wanting to improve things and needing to focus on the assigned tasks. Another commenter framed the problem as a form of "yak shaving," where developers get sidetracked by seemingly small improvements that snowball into large, time-consuming projects. They suggested the importance of focusing on the bigger picture and resisting the urge to get bogged down in minor details, especially when starting a new role.
The discussion also touched upon the challenge of balancing improvement efforts with the need to maintain existing systems. One commenter noted the difficulty of justifying time spent on refactoring or improvements when there's pressure to deliver new features. They also highlighted the potential for well-intentioned fixes to introduce new bugs or regressions. This sentiment was echoed by another user who emphasized the importance of considering the potential risks and trade-offs before embarking on any "fixing" endeavor.
Some commenters offered practical advice for managing the "curse of knowing how." One suggestion was to create a dedicated backlog for improvement tasks, allowing developers to capture their ideas without derailing ongoing projects. This approach allows for prioritization and discussion with the team about the best way to address these improvements. Another commenter advised setting clear boundaries and communicating proactively with stakeholders about the scope of work and the potential impact of undertaking additional fixes. They stressed the importance of having open discussions about priorities and trade-offs to avoid misunderstandings and ensure alignment.
Finally, a few commenters offered alternative perspectives, suggesting that the "curse of knowing how" can also be a valuable asset. One commenter argued that experienced developers have a responsibility to identify and address technical debt, even if it's not explicitly part of their assigned tasks. They emphasized the long-term benefits of maintaining a clean and well-structured codebase. However, they also acknowledged the importance of balancing this with the need to deliver business value and avoid unnecessary disruptions. Another commenter pointed out that the "curse of knowing how" can be a sign of passion and a desire to create high-quality software, suggesting that it's a trait that should be nurtured, not suppressed. They emphasized the importance of finding a healthy balance between fixing things and focusing on the core objectives.