Comments 1 - 2 of 2 Search these comments
I find that complexity is death.
The more moving parts, and the more obscure their interaction, the more likely the system is going to go down.
Many developers fall for the latest bright and shiny thing, convince their employer that it's OK, and then get bit by some interaction they had not considered, because they just doubled the possible number of interactions.
Les is mor.
I am wondering if the credit union has some H1-B's screwing things up behind the scene. That's what you get for hiring cheap labor.
A good example of software testing, a number of years ago I was doing some work for a major pharmacy company. Had their applications failed in production, it would have impacted at least half of the country (Walgreens, Walmart, etc). When we got the approval to move the code into production, a developer would be at the data center actually doing the move. I had a two hour time frame in the middle of the night, to stop all applications, move the objects, restart the system, and make sure that all was working correctly. We never once had a major issue that I can think of.