4 ms·

> The only code you never have to touch again is code nobody is using. There are plenty of counter-examples, but I like the example of video games. https://ww

> The only code you never have to touch again is code nobody is using. There are plenty of counter-examples, but I like the example of video games. https://www.polygon.com/2020/1/13/21064100/vvvvvv-source-code-game-development-terry-cavanagh-release https://www.polygon.com/2020/1/13/21064100/vvvvvv-source-cod... There's a pretty clear ship date, after which you never touch it again. Even in the world of SAAS, there are plenty of services or libraries that you write that serve a single purpose, are good enough, and never get touched again.

wpietri 7y ago
Well, some video games, those based on a historical model of actually shipping physical games. But successful video games these days can literally run for decades, either directly (as Warcraft) or as a series (like Madden NFL). Plenty of things that are intended to be one-and-dones also evolve, like Stardew Valley's audience demanding multiplayer. Even the code you mention isn't a great example for your case. In theory it was throwaway, but now that it's out there, you can bet that plenty of people will be touching it. And you're also ignoring the path not taken. This beloved game didn't get a sequel, despite plenty of demand. If the code were in better shape, might it have had one?