Beyond Favorites: Why Being Open-Minded Makes You a Better Developer
Dr. Kai Dupe • September 18, 2025
Instead of devotion to one technology, developers should cultivate adaptability.
One of the most exciting aspects of working in technology is also one of its greatest challenges: change is constant. New frameworks, languages, and tools appear every year, often promising to make development faster, cleaner, or more powerful. With so many options, it’s tempting to pick a favorite and hold onto it like a badge of honor. But while having preferences is natural, becoming “religious” about technology—treating one tool as superior in all circumstances—can limit growth and opportunity.
John Sonmez, author of The Complete Software Developer’s Career Guide
(2017), explains this pitfall clearly: “Too many developers get religious about their tools”—treating languages, frameworks, or methodologies as the only right way. He warns that this mindset not only creates unnecessary division but can also stall a career and prevent real growth.
Technology is constantly evolving. The tools that dominate today may be outdated tomorrow. For example, COBOL once ruled enterprise systems, yet many new developers have never touched it. More recently, frameworks like AngularJS gave way to React and Vue, while artificial intelligence and cloud computing are reshaping entire industries. If a developer ties their identity too strongly to a single language or platform, they risk being left behind when the industry shifts.
Instead of devotion to one technology, developers should cultivate adaptability. Being flexible allows you to evaluate each project on its own merits and choose the best tool for the job. This not only makes you more effective, but also more valuable in the job market. Employers seek problem solvers who can navigate multiple ecosystems, not zealots who refuse to look beyond their comfort zones.
As Sonmez reminds us, technology is just a tool—nothing more. A good carpenter doesn’t obsess over one hammer; they master the entire toolbox. Likewise, a good developer learns multiple languages, frameworks, and practices, always keeping in mind that the end goal is solving problems and creating value for people.
Ultimately, resisting the urge to be religious about technology fosters collaboration, humility, and continuous learning. It keeps us focused on what matters most: writing software that improves lives, businesses, and communities. In the end, your greatest strength as a developer is not your loyalty to one stack, but your ability to adapt, learn, and deliver results in a world of constant change.
A mentor gives you advice. A sponsor creates opportunities.
Representation alone will not solve the persistent racial disparities in computing.
The truth is that most software applications exist to manage information.
Artificial intelligence has become the newest member of nearly every software development team.
The true promise of computing is not found in the machines we build, but in the human potential we unlock when knowledge becomes accessible to everyone.
One of the reasons I value the MCT program so highly is that it represents more than technical knowledge.
Software engineering is not simply coding.
Companies often promote the idea that technical skill alone determines success.
Hackathons also strengthen teamwork and communication skills.
Stepping onto the campus of Morehouse College this past weekend for Admitted Students Day was more than a visit—it was a moment of reflection. As I watched young Black men walk with purpose across the yard, I found myself asking a simple but profound question: What would it have been like for me to study computer science here? My journey into computing was shaped in environments where I was often the only Black man in the room. That reality brings with it an unspoken weight—the need to prove you belong, the awareness of being watched, and sometimes, the quiet isolation that comes with underrepresentation. Standing at Morehouse, I realized that this burden is not a given. It is a condition of the environment. At Morehouse, the environment is different by design. Here, Black men are not anomalies—they are the standard. I imagined what it would feel like to learn algorithms, data structures, and software development in a space where my identity was not questioned but affirmed. Where excellence is expected, not in spite of who you are, but because of it. As a computer science professor, I understand the academic rigor required to succeed in this field. There is no shortcut through recursion, no bypass around debugging, no substitute for disciplined problem-solving. But what struck me during my visit is how much context matters. When students are free from the psychological burden of proving they belong, they can redirect that energy toward mastering the material. They can collaborate more openly, ask questions more freely, and take intellectual risks without fear. I also thought about legacy. At Morehouse, students walk the same grounds as Martin Luther King Jr.. That kind of history does something to a person. It raises the bar—not just academically, but personally. It invites students to see their education not just as a pathway to a career, but as preparation for impact. Leaving campus, I felt inspired—but also reflective. I cannot rewrite my journey, but I can appreciate what spaces like Morehouse offer the next generation. For a Black male pursuing computer science, it is more than a degree. It is an opportunity to develop skill, confidence, and identity in alignment. And that combination is powerful.