Business Understanding: The Missing Skill in Many Developers
I still vividly remember one of the interview sessions I had back in 2023. At the time, I was applying for a position as a fullstack developer at a well-known hospital. During the interview, I explained why I was interested in joining and shared my concern about how critical hospital systems are. I mentioned that if the system is not properly built, it can become a major obstacle for the clients — in this case, the patients. Not all patients are able to tolerate or adapt to an incompetent system, especially considering they are already in a vulnerable condition where they need fast, seamless, and comfortable service. This perspective comes from understanding the psychological state of patients who are unwell.
I expressed my concern that if a system is not well-designed, the impact can be highly detrimental. In other sectors, a bug might just be an inconvenience. But in a hospital, a bug can become a serious barrier for patients trying to receive fast and comfortable care. Patients come in under less-than-ideal conditions, and that’s precisely when the system needs to be at its most humane. Unfortunately, not all hospital information systems are built with this kind of understanding.
What I said at the time wasn’t merely a personal opinion — it came from my own experience when I sought treatment at a hospital in my hometown.
Lessons from a System That Was Misunderstood
A few months after that interview experience, I was involved in maintaining and fixing bugs in an internal information system. Technically, my team and I succeeded in resolving a variety of issues. All fixes were done with a systematic and efficient technical approach.
However, just a few weeks after deployment, complaints from internal users began to rise. Instead of making the system bug-free, our fixes introduced new problems that significantly disrupted internal business processes.
It turned out that in the process of fixing those bugs, we had been too focused on technical standards without conducting proper testing. We had repaired the system from a technical perspective — but unknowingly broke it from a business functionality standpoint.
That became a turning point for me. I realized that in any maintenance or bug-fixing process, understanding the business model and operational workflows is a critical foundation. Without it, a programmer is reduced to being just a code repairman — not a real problem-solver who understands the field.
Business Model: A Map Every Developer Must Master
As time went on and I gained more experience in various system development projects, I began to realize that technical skills alone are not enough. In a revamp process, for instance, understanding the operational workflow and business priorities becomes the compass that guides our decisions. Without that understanding, we might remove features that are actually vital to users, or add something that only complicates workflows without offering real value.
When designing a new feature, certain fundamental questions must always be our guide: Does this feature support the revenue stream? Does it solve an existing bottleneck? Or is it merely a “nice to have” addition that’s irrelevant to the core business needs?
The same principle applies in maintenance. Understanding the business model helps us make smarter prioritizations. Not every bug needs to be fixed immediately — only those that directly affect users and disrupt critical operations should be addressed first. The rest can be scheduled for later releases.
Without a clear map of the business model, developers are prone to fall into narrow technical assumptions. But a great system isn’t just about clean code architecture; it’s about how well it responds to the real needs of the business it’s built for.
Since then, I’ve made it a habit to train myself to ask questions, listen closely, and read the situation — not just from a technical perspective, but also from an operational and business point of view. I started asking users directly, digging into process flows, and even trying to understand the company’s revenue logic behind every feature request.
Closing:
Being a great programmer is not just about mastering the latest technology or writing efficient code. More importantly, it’s about understanding the context in which that technology is applied. Information systems — regardless of their form or scale — are always built to meet human needs and support business operations.
When we start viewing our work through the lens of operations and business models, we move beyond being mere “feature builders” and grow into strategic partners who can deliver real impact. That’s where our true value as developers begins to shine.
