What software development strategies has Sony employed to ensure that its products remain cutting-edge?
I remember hearing a story about a step in the QA process at Sony Interactive.
- They would start playing a game.
- Then, during play they would pause it.
- Then they would press eject on the game disc, opening it.
- Then leave it like that for 24 hours, game paused, disc drawer open.
- Then come back to it, close the disc drawer, un-pause the game and continue playing.
If that didn’t break or crash the game or cause any issues, it was an indication that the game was reasonably stable. Buggy software with memory leaks isn’t usually robust enough to withstand that kind of behaviour. You have to try and imagine what the average kid who treats the system like a toy will do, and think up bizarre use cases to test against, and that was quite a good one, apparently.
Though like I said, something I heard from a project manager I worked with once.
Unless anybody at Sony Interactive is reading this and can shed some light?
Originally posted here