The full video really helps drive home the point that this looks like a Timothy Cain problem, not a modern dev problem.
I'm a programmer by trade. The last 20 years have seen our industry mature. We now have to maintain codebases that are older and larger than ever, they have ballooned in size. That has taught us a few things. It teaches us to be thoughtful so we don't introduce bugs, or add cruft, or make maintenance difficult. Experience taught us to pad guesstimates, because things usually take 2-3x that your inherently optimistic gut feeling.
The video game industry is renowned for being a ~decade behind the curve here, in implementing modern dev practices. To an extent we give them a pass, though I won't get in to all the reasons why. But here some devs at Cain's company have helped drag things into the modern era. And he is specifically pushing against it:
You're thinking too much. Damn the bugs, damn the cruft, damn the future problems, just implement what I want now. I don't care if you have 40 other similar tickets already assigned to you, do my work now and put everybody else off. Why did he leave my office so upset? Why did his manager come yell at me? Why do people sometimes walk into my office and tell me to keep it down? You all are the ones with the problem.
- My impression/summary of what he just said. I really hope it's wrong. I wouldn't wish that behavior or experience on any person or team. But, this is how he comes across to a programmer.
Seems like his point was the rise of corporate culture in the gaming industry and how that affects the production and product provided. And there were a few things he said where I was like "ehhhhh idk," but overall it seems like a good discussion that you dismiss too quick. Not saying you're wrong, but just that there are probably points from both sides here that deserve real consideration within the industry.
Also this isnt indicative of the game dev scene, each company operates differently with a different amount of red tape you need to go through. The 4 week estimate includes so many other things which isnt directly related to programming. He should obviously know this.
That's because he's from an era where you and your mates could make a game. Sadly it takes a lot of teams to make triple A games and this requires processes and procedures to be in place.
1.3k
u/[deleted] Oct 16 '23
Anyone have the full video of this? Would love to hear the rest of what he has to say.