Can Programmers Be So Smart They Fool Themselves?
Soft Skills • Software Development Career Advice
We can feel so strongly about experiences we've had, that they blind us from being open to other equally valid perspectives
Watch or listen to this episode
YOUTUBE
SPOTIFY
APPLE
Five Mindset Limitations That Can Sabotage Your Tech Career
In my years of working in the software industry, I’ve seen it all: from the intense pressures of learning on the job to the subtle traps of overconfidence. One of the biggest lessons I’ve learned is that mindset is everything. Your beliefs and attitudes can either propel your career forward or hold you back in ways you might not even realize. Today, I want to share five mindset limitations that are particularly common among programmers and tech professionals. These limitations can cloud your judgment, lead you to make poor decisions, and ultimately stifle your career growth. Let’s dive in.
Binary Thinking: The Trap of “Only This or Only That”
One of the most common mindset traps in tech is binary thinking—the idea that there are only two opposing options, and one must be correct while the other is wrong. This kind of thinking is prevalent in our industry, where strong opinions often dominate discussions. Whether it’s the classic debate over “tabs versus spaces” or more significant architectural decisions, binary thinking can limit your ability to see the full picture.
I’ve fallen into this trap myself, especially early in my career. I held strong opinions about the “right” way to do things, often dismissing alternative approaches without considering the context. But as I’ve gained more experience, I’ve realized that many of these decisions aren’t black and white. There are often multiple valid approaches depending on the specific situation.
If you find yourself thinking, “This is the only way to do it,” take a step back. Consider whether your belief is based on solid evidence or just your personal experience. More often than not, both sides of an argument have some merit, and the best approach lies somewhere in the middle.
Overconfidence in Anecdotal Evidence
Another mindset limitation is placing too much confidence in anecdotal evidence—relying solely on your personal experiences to guide your decisions. This is especially dangerous in tech, where the complexity of projects and the variety of contexts mean that what worked for you in one situation may not work in another.
For example, just because a particular framework or methodology worked well on one project doesn’t mean it will be successful on another with different constraints and goals. I’ve seen developers, including myself, make the mistake of assuming that their past successes automatically translate to new situations. This overconfidence can lead to conflicts with team members and poor decision-making.
It’s essential to recognize the limits of your experience. Whenever possible, seek out broader evidence—peer-reviewed studies, industry reports, or simply feedback from a diverse group of professionals. This approach not only strengthens your decisions but also makes you more open to learning from others.
Absolutist Stances: Closing Yourself Off to New Possibilities
Absolutist thinking is similar to binary thinking but takes it a step further. It’s the belief that there’s no exception to a rule you’ve formed, often based on a few negative experiences. For instance, after dealing with a few bad managers, you might conclude that all managers are incompetent and that management, in general, adds no value to a project.
This kind of thinking can be incredibly limiting. If you assume that all managers are bad, you’ll approach every new manager with distrust, which can strain your working relationships and close you off from valuable mentorship. The same goes for any other absolutist belief you might hold—whether it’s about certain programming languages, tools, or methodologies.
The key is to remain open-minded and adaptable. Just because you’ve had a few bad experiences doesn’t mean that every similar situation will turn out the same way. Try to approach each new project and team member with a fresh perspective, allowing yourself to see the unique value they might bring.
Recency Bias: The Illusion of “Newer is Better”
In our fast-paced industry, it’s easy to fall into the trap of recency bias—the belief that newer is always better and that past knowledge is obsolete. This mindset can lead you to adopt the latest trends or tools without fully understanding their limitations or how they fit into the bigger picture.
I’ve seen this play out with programming paradigms like object-oriented programming (OOP) and functional programming. When functional programming gained popularity, some developers were quick to dismiss OOP as outdated, forgetting that each paradigm has its strengths and weaknesses depending on the context.
Recency bias can cause you to overlook tried-and-true methods that may still be the best solution for certain problems. While it’s important to stay current with industry developments, it’s equally important to critically evaluate new ideas and understand their place alongside established practices.
Vanity Metrics: The Danger of Focusing on the Wrong Numbers
Finally, let’s talk about vanity metrics—those numbers that look impressive on the surface but don’t tell the whole story. In tech, this might be the number of lines of code you’ve written, the number of features you’ve shipped, or even the prestige of the company you work for. While these metrics can give you a temporary sense of accomplishment, they often fail to reflect the true impact of your work.
For example, if you’re working at a large tech company, it’s easy to get caught up in the prestige and the high salary. But if the work environment is toxic or if you’re not learning and growing, those impressive numbers won’t mean much in the long run. Similarly, in a startup, focusing solely on customer sign-ups without considering retention rates can give you a false sense of success.
To avoid the trap of vanity metrics, focus on what truly matters: the quality of your work, the relationships you build, and the value you create for your users and clients. These are the metrics that will sustain your career over the long term.
Conclusion
These five mindset limitations—binary thinking, overconfidence in anecdotal evidence, absolutist stances, recency bias, and vanity metrics—can subtly sabotage your career if you’re not careful. By recognizing these traps and actively working to overcome them, you can make better decisions, build stronger relationships, and enjoy a more fulfilling and successful career in tech.
About the THRIVING TECHNOLOGIST show
On YouTube and all major podcast networks, Jayme shares teamwork and leadership strategies, guidelines for healthy company culture, and stories about real projects so you can have a sustainable career in the software industry.
Jayme Edwards
A family man and veteran of nearly 40 software projects, Jayme experienced many wins and losses over his career as an architect and consultant.
Now he's coaching software developers, managers, and business owners to overcome challenges in the IT industry - so they keep growing.