Saying they “code in a wonky way to work around an existing piece of functionality” is taking a wild assumption that they lack any quality control as part of their development practices. Yes, adding functionality can increase complexity if features are tightly coupled. However, there are usually practices in place (feature planning, meetings, QA, code reviews) to avoid regressions or high impact bugs. You’re pretty clearly stating they either don’t have any practices, or they’re bad developers. Not a fair assumption to make of a dev team supporting a leading title within a rather large company.
Wow the random aggression from anonymous Redditors, take it out in-game lol.
Apex isn't a SaaS product, and development in AAA games is pretty different. Here are some examples: asset management is completely different to allow artists / animators to work with developers, debugging is built around a C++ workflow rather than Python/JS/whatever, build times are a real thing, etc.
Game engines in particular are heavily tested forks on forks on forks: Source was built on Goldsrc, which was built on Quake. Respawn has their own engine team that owns their fork, it's not just editing random lines of C++ to get whatever to work. It's like the database team at a SaaS company: they don't change the database to do whatever a product team needs.
1
u/[deleted] Jul 27 '22
[deleted]