« prev   random   next »

1
0

Testing and software development

By MAGA following x   2018 Mar 15, 1:45pm 981 views   2 comments   watch   nsfw   quote     share    


My credit union just "updated" their website for online banking. Talk about your buggy code. As a mainframe developer supporting tens of thousands of users, I can't imagine letting something this bad go into production. Not only did we have testing at the development level, our code is released to QA for further testing. We have numerous formal tests that the application needs to pass before being approved for production.

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.
1   Patrick   ignore (1)   2018 Mar 15, 2:28pm   ↑ like (1)   ↓ dislike (0)   quote   flag        

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.
2   MAGA   ignore (1)   2018 Mar 15, 5:24pm   ↑ like (0)   ↓ dislike (0)   quote   flag        

Patrick says
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.



This project is not going to go well for the government and taxpayers. Mark my words. :-(


https://www.usatoday.com/story/news/politics/onpolitics/2017/06/05/va-taps-cerner-new-veterans-medical-record-system/102516784/

http://www.healthcareitnews.com/news/va-cerner-ehr-deal-held-after-spat-over-interoperability-definition-report-says

about   best comments   contact   one year ago   suggestions