What would I change about software development now to program like they did 50 years ago? I would program like they programmed 50 years ago: assume it has to work. Assume updates will be risky and expensive. Build in failsafes and watchdogs and redundancy. Be able to replicate the build every year for 50 years. Train people to know what the logs really mean, every year for 50 years. And launch it before the bike shedding can begin!
I find the killer feature to be the ability to pause games. Sure, I could do that on my PC, but since this whole Deck is dedicated to just running the game, and I can set it aside, do the thing I need to do (maybe on my PC) and come back and start right where I left off, it feels different, more integrated, because for a little while, the game state and the deck state are the same. It is less like the Deck is running the game and more like the Deck is the embodiment of the game.
Almost 50 years old now, and still sending data.
What would I change about software development now to program like they did 50 years ago? I would program like they programmed 50 years ago: assume it has to work. Assume updates will be risky and expensive. Build in failsafes and watchdogs and redundancy. Be able to replicate the build every year for 50 years. Train people to know what the logs really mean, every year for 50 years. And launch it before the bike shedding can begin!