The gaming industry also makes a strong argument in favor of flipping the concept stage of your design process on its head. Before the first logic gates are laid out, every possible source for game and console design inspiration is explored. Form usually follows function, but sometimes it’s appropriate to let form shape function. Many user-facing apps that start life as code would fare far better if the first step in their evolution had been to create a GUI prototype. After all, much like gamers, users who are captivated by the software they use are motivated to attain higher levels of competence, translating into more time spent with the software they’re paid to use and less time trying to escape from it with IM and surfing.
Another takeaway worth nothing is that game consoles never get attacked by malware. In the main, even when they are visible to the Internet for community gaming, no malicious effort survives a reboot. IT can easily borrow this lesson. Marking a file on a hard drive read-only is merely a switch that a cracker or in-house thief can flip at will. But if you store privileged executables and exploitable configuration files, or an entire VM image, on read-only or write-once flash or optical media guarded from physical access, even a cracker that knocks down all your walls can’t create a back door.
But can’t somebody boot with an altered copy of the DVD? Think like a game console engineer and solve that problem yourself.
-- Tom Yager