Proprietary information systems like Wells Fargo’s do not magically appear. These systems are not purchased in shrink-wrapped boxes. They are custom-coded and glued together with immense effort by people in cubes, and they cost money. Lots of money. They are also risky to develop. For these reasons, corporations establish formal processes for systems development, deployment, and maintenance of information systems. These processes are heavy-weight. “Agile” they will not be. Scrums will not figure largely in them. There are many methodologies for such processes, but there will be two common feature shared by all: They will be documented, each step of the process will be documented, and major documents — for example, accepting a requirements analysis or a decision to deploy — will be agreed and signed off on at the executive level. CYA is the order of the day. (And if none of that is true, so much the better.)
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×
Presto Vivace writes: "In his Code is Law post, lambert strether discusses how banksters use proprietary code to apply mortgage payments to fees and interest first, even when that is against the mortgage contract. This creates a bias towards foreclosure and computer code supersedes legal code. It is a long post which goes into the details of how this comes about.