Why Web developers must understand business too
I see and hear about it too often. The typical stereotype of a Web developer or software engineer is a pocket-protector, glasses, algorithms, socially awkward and tends to be an introvert. These individuals are generally portrayed as out-of-touch when it comes to how their work truly has an impact on the business of their company. The guy portrayed to the right still rings true in modern pop-culture on what a nerd, Web developer or software engineer is like.
During my tenure at Ball State University I primarily studied code, applications and databases. I was completely on my path to Nerd City (does not really exist...I think). I opted to also study Information Systems Management to get a better feel for how IT and software engineering really impacts business. I actually saw quite the dynamic between most engineers I was studying with and the students that took the Information Systems Management courses. The students in IS Management generally understood practical business applications of IT and software engineering more than those who did not study IS.
Why is this important? I am always trying to find ways for the work I do to have a positive impact or effect on my company and our clients. Understanding practical business elements of a project it harnesses my focus to deliver more reliable code in the end. Many times Web developers and software engineers can get so hammered by the details of classes, objects, third-party applications, algorithms and the question of "does it work" rather than "why does it need to work"?
If you are in Web development or software engineering try to take a moment on the next project and think why does this client need this feature? The answer will almost inevitably give you more focus and a better understanding of what you need to do. The steps will become more clear on how to get to the end result. The question of "does it work" is still important in the end as you don't want to deliver a product that simply fails, but the question of "why does it need to work" will expand your insight on a project to catch potential traps or better methods to deliver a better product.





