Why can two pieces of game dev advice seem contradictory but both still be correct? A) Because most game dev advice is completely useless B) Because the correct answer often depends on context, timing, platform, and the specific game C) Because only advice from successful developers matters D) Because every game should follow the exact same marketing strategy (answer in reply below)

#### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### #### ANSWER #### (B) A lot of game dev advice sounds contradictory because people remove all the nuance. Advice that works for one genre, one platform, one budget, or one point in time might not work in a different situation. The important thing is not just asking "Is this advice true?" but asking "What is the context for this advice? And does it apply in my case?"

@UnityCodeMonkey I'd argue that listening to successful devs can be a mistake, because they often have advantages that a solo dev doesn't. Would you tackle game dev the same way Rockstar, a multi million dollar company, would?

@UnityCodeMonkey E) Because every “never” eventually becomes someone’s GDC talk.

@UnityCodeMonkey The weight of advice depends on who's saying it