If you're in trouble and cannot find an answer to a question which goes beyond Stack Overflow...

If you have a not-so-usual solution for your problems but need to justify it to your boss...

If you like to think on your own rather than blindly follow "common wisdom" and "profound truth"...

...then 'No Bugs' Hare on Soft.ware might be the right place for you.

Your mileage may vary. Batteries not included

Development, page 2:

Choosing Version Control System for MOG development

posted September 19, 2017 by "No Bugs" Hare

Quote:	“For game development (and unlike most of other software development projects), you’re likely to have binary files which need to be edited (representing so-called “assets”)”
Another Quote:	“for open-source games, Git does have a Very Significant Advantage™”
	[→]

posted September 12, 2017 by "No Bugs" Hare

Quote:	“As a rule of thumb, for gamedev we DO need to have our version control to be easily usable by non-developers.”
Another Quote:	“it is the second developer to commit who becomes ~~a rotten egg~~ responsible for resolving conflicts”
	[→]

posted June 6, 2017 by "No Bugs" Hare

Quote:	“This communication channel (coming from Operations back to Development) is extremely important to have a game which is able to work anywhere-reliably in the real world”
Another Quote:	“Most importantly, our processes should allow these different production cycles to co-exist.”
	[→]

posted March 28, 2017 by "No Bugs" Hare

Quote:	“BTW, I don’t want to say that unit testing is pointless”
Another Quote:	“I am arguing that changing design to enable testing should be avoided.”
	[→]

posted August 2, 2016 by "No Bugs" Hare

Quote:	“you MUST NOT edit any of intermediate files directly”
Another Quote:	“How will I implement automation?”
	[→]

posted July 25, 2016 by "No Bugs" Hare

Quote:	“Yes, a coding architect might work (and is indeed orders of magnitude better than an architect who has no clue about the code), but a knowledge-sharing architect will generally work better.”
Another Quote:	“As a nice side effect, the very same knowledge sharing weakens a dependency on the architect (and reducing any dependency on a specific person is a Universally Good Thing™).”
	[→]

posted June 6, 2016 by "No Bugs" Hare

Abstract:	“After bashing all those Big Name guys for making those over-arching sets of guidelines, it is perfectly logical for me myself to do the same 😉”
Quote:	“DON’T use C-style cast, EVER. If you DO need a cast – DO spend time on figuring out which of C++ *_cast<>s you really mean (and maybe, you’ll find a way to avoid that cast at all)”
	[→]