James is a pompous douche who seems to have about the same knowledge of games as most "games analysts" a la Mark Brown who try to talk about mechanics and game development when they haven't even made any games. It really comes off in some of the more controversial episodes. It's a shame, because it's sorta impacted my view on Dan who is actually a pretty nice (and actually talented) guy from what we've seen in like the Side Quest videos and other things where he actually speaks for himself.
It's interesting to look for times James admits his lack of expertise; a lot of the technical videos or videos about dev problems open with things like "when James was working with a team whose game just wasn't coming together," as if he's some magical game shaman even though he's never made any games, or "at a talk James got asked about how to fix (x problem in development) and we thought it was interesting enough to answer again here". It's never anything like "once while making a game, James encountered x" or "in our experience, x is a good way of doing things".
I also found this nugget while looking on their Wikipedia page. Guess it hasn't been updated in a while...
It's interesting to look for times James admits his lack of expertise; a lot of the technical videos or videos about dev problems open with things like "when James was working with a team whose game just wasn't coming together," as if he's some magical game shaman even though he's never made any games, or "at a talk James got asked about how to fix (x problem in development) and we thought it was interesting enough to answer again here". It's never anything like "once while making a game, James encountered x" or "in our experience, x is a good way of doing things".
I also found this nugget while looking on their Wikipedia page. Guess it hasn't been updated in a while...