4 ms·
I'm going to preface this post with a note that, yes, there are surely good developers in game development, this is not a universal thing, etcetera etcetera. A
by eropple 12y ago
I'm going to preface this post with a note that, yes, there are surely good developers in game development, this is not a universal thing, etcetera etcetera.
Ass properly covered, I'll be real: I'm never surprised to see this because "code reuse" is generally the sign of reasonably advanced developers and I don't know a single person in game development I would hire for a role outside of it. It's not just NIH--that's a problem but one slowly going away. It's more just a fundamental lack of understanding of software engineering and building Good Code. As time goes on I've seen gamedev acquaintances poorly reinvent most of the wheels that the rest of the world takes for granted--even something as simple as serialization for save data and network transport (but no schematic validation, because "schemas suck") was trumpeted to me as this Big Crazy Great Thing. Which contextually it may be, but I kind of feel like the state of the art for stuff not involving pointer munging is about a decade behind everybody else.
So, code reuse? Gotta make good code first.
- alexnking 12y agoWell there's a difference between code reuse, and cross-platform code reuse. If you're porting a Laravel project to Rails or vice versa, you should be reusing logic, not code.
- pmelendez 12y agoI worked in the gaming industry for a couple of years and after I worked in the RTB industry and lately in the forex industry. I am not alone, and I have a lot of friends coming out of gaming that work very well in other industries. The problem is not whether or not game developers know how to reuse code but whether or not it makes sense or are allowed to reuse it. One big challenge when you are going to reuse code is not having a stable set of requirements (which in gaming is almost non existing even in the late stage of a project) and when you take that and join it with tight and unreasonable schedules you would have a huge mess as result. The state of the industry is very unhealthy in my opinion and I wouldn't be surprise if there is another dark age for videogames coming up.
- SimpleMinds 12y agoI agree with what you said with my limited experience. I hope it's anecdotal nature is good enough. I worked in a company that went from doing software gigs in general to be full mobile gaming company. Before it was quite standard Agile style company: Scrum, code reviews, TDD, cross-functional teams (front end devs knew how servers works in general), focus on quality over quantity (one dev, rotated weekly or biweekly, focusing on fixing bugs), separate concerns. After going full game-oriented, company hired couple of people from gaming industry into higher positions - tech leads, project managers etc. Over couple of months, people with many years of experience in those big companies dismantled what was standard for me, using combination of two arguments: - big names don't do it, so it must be wrong - it's a waste of time Before I quit, there were no longer code reviews (waste of time), all testing was to be handled by QA team (waste of valuable dev time), ship with issues (waste of time to fix minor bugs when can add features), single system responsibility (one dev to write code for client server protocols, one dev for UI, one dev for assets etc, that's gow big names do it). At one of the last talks with "industry veteran", when I mentioned those things - and how negative, in my opinion, those changes are, his response was "so you are saying that whole gaming industry dev practice is wrong". At that point I thought he's right and I sound full of crap, now I believe that yes, AAA companies are simply bad development practises shops. My guess as to why is because AAA is very strongly driven by deadlines and marketing, where you cannot simply delay release (Christmas shopping spree is coming). This idea I saw articulated on HN first and I agree with it.
- pandaman 12y agoIf the AAA practices had been so bad then, by now, we had Agile-TDD-etc shops taking their lunch and driving them out of business. As of now there is just one studio practicing Agile, Blizzard. If it is not known, Blizzard is also famous for incredibly long projects and missing deadlines. I had personally observed collapse of two Agile AAA studios, who, while doing pretty well by the industry standards, did not have the super-profitable titles to hold them up during 5+ years of development cycle. So I believe we have the AAA practices not because game programmers are stupid but because studios that don't use them are not around for long.
- 12y ago
- smacktoward 12y agoThis seems unsurprising, given the game industry's notorious reputation for developer burnout. The developers don't know how to write good code because by the time they've learned they've burned out and left the industry. They're then replaced by clueless young people, and the cycle repeats.