You just developed a smart ETL process and met your project schedule on time. After months of attending meetings that imparted you little technical kick you finally got to satisfy the “techno-geek” inside you. The solution you suggested for the problem in those meetings has finally made it into production and the release went without a blip. Those who debated against your solution seemingly have vanished and declined your invitation for drinks on the occasion of the successful release. You can’t wait for the rounds of appreciation mails that will soon follow for such a timely and smooth release of the complicated project.
A major occupational hazard inflicting a Software Programmer is the constant craving to develop software that is complicated even if to solve a simple problem. The satisfaction derived out of a complicated solution can only be subsumed by another even more complicated solution and a vicious cycle is guaranteed to ensue.
The result is a complete ignorance of supportability, maintainability and readability of the software program. One aspect of software programs is their very short life but this somehow seems a forgotten point even by the most skilled of developers. Generally, it is those who are most skilled that build programs with a pride that ignores the rule of short life assuming what they have built to be everlasting.
Often, it is those of the lesser skilled developers who tend to develop the program in simpler components which by definition are easy to maintain, support and readable. Perhaps they may not scale or may look downright disgusting to the better skilled, but ask any support manager which brand of developers they prefer and the answer may be a bit un-comfortable to those hot shot coder crowd.
Not to conclude but to just begin the discussion, keeping the code simple is more difficult than writing complicated programs.
Use Undraleu® to perform an Automated Code Review of your Informatica PowerCenter Code and get a best practices perspective on the health of your ETL code