AJack10600
Elite
- Joined
- Jun 13, 2005
- Posts
- 2,732
- Location
- Switzerland
- Society
- SPU ¦ Smart Professionals United
- Avatar Name
- Larios Semai Niva
Following yet another unbelievable code bug after a release I can not help myself but to be astounded as to how MA or FPC run their Code Releases ...
In every release we have known bugs and issues, and now we get a major revamp and it totally fails...
Now I am not in the gaming industry, but I have some interaction with critical software development.
I work in an area where I am at the interface of the business and IT and I deal with this stuff quite a bit.
Firstly, when we change things in code in an application there is a concept called 0 Impact Testing. This should prevent any old code from being corrupted or changed.
On top of that we have like 3 Test environments, an unlimited amount of test runs in the first 2 until you sign off.
Then another 3 Production Like Test runs in a PRD equivalent Testing environment. Then a regression run. Only when all these items work and are signed off, will an item be promoted to Production...
On top of that we can ICE new code or immediately rollback code when it cocks up....
I just don't understand how they can ignore all this... How on earth do they run their Releases ? I'd really love to know... :roll:
Do they need an IT project manager ? This all seems like schoolboys programming code... Sorry but I can't help it... Error is human, it happens... but in IT you need to minimise the errors to a max. Why does this keep happening ?
In every release we have known bugs and issues, and now we get a major revamp and it totally fails...
Now I am not in the gaming industry, but I have some interaction with critical software development.
I work in an area where I am at the interface of the business and IT and I deal with this stuff quite a bit.
Firstly, when we change things in code in an application there is a concept called 0 Impact Testing. This should prevent any old code from being corrupted or changed.
On top of that we have like 3 Test environments, an unlimited amount of test runs in the first 2 until you sign off.
Then another 3 Production Like Test runs in a PRD equivalent Testing environment. Then a regression run. Only when all these items work and are signed off, will an item be promoted to Production...
On top of that we can ICE new code or immediately rollback code when it cocks up....
I just don't understand how they can ignore all this... How on earth do they run their Releases ? I'd really love to know... :roll:
Do they need an IT project manager ? This all seems like schoolboys programming code... Sorry but I can't help it... Error is human, it happens... but in IT you need to minimise the errors to a max. Why does this keep happening ?