Another month, another rationality quotes thread. The rules are:
- Please post all quotes separately, so that they can be upvoted or downvoted separately. (If they are strongly related, reply to your own comments. If strongly ordered, then go ahead and post them together.)
- Do not quote yourself.
- Do not quote from Less Wrong itself, HPMoR, Eliezer Yudkowsky, or Robin Hanson. If you'd like to revive an old quote from one of those sources, please do so here.
- No more than 5 quotes per person per monthly thread, please.
- Provide sufficient information (URL, title, date, page number, etc.) to enable a reader to find the place where you read the quote, or its original source if available. Do not quote with only a name.
It's accurate but not very precise, in the same way that the story about how there are wet streets and rain is true but misses the inner connections. Many people fail to get the distinctions between programmers, artists, and designers, because they want designers to fix bugs, just shift staff to design, etc. And testers are nowhere in that simplified model. So people have enough of an idea to get the wrong idea.
Many game developers have a shaky idea of how game development works once the team is larger than can work in one room. That becomes project management, and if you ever want to to see the planning fallacy in all its glory, follow game development and the timelines of when things will be ready. Showing off my own availability bias, the first example that comes to mind is this game, which was "two months from beta" three years ago and has yet to release. Heck, last week's big story in game development was the PC port of Batman: Arkham Knight, a major release that had to be taken off the market and is now labeled as available this fall. They had to revise the release date after releasing.