I agree - maybe some modern game engines have unit tests for stuff like their physics engine and their "standard library" code (optimised data structures, maths utilities, string utilities etc) but as others have said, testing sound and vision is hard, and something that hasn't been mentioned is all the different flags in a game engine - testing even a sensible subset of all the different sound and rendering variables would be a huge undertaking.
Gosh, I don't think any game engines have particularly good test suites at all. GoldSource and Source are the only ones that I have any real experience with and neither seems to have anything (Source may have a handful of things but nothing approaching baseline let alone comprehensive).
I have no idea how game devs handle big refactors other than lots of manual testing.
I vaguely remember being told to put assignments in a drop box (like a mail box on campus) in the mid 2000s at least, and I'm sure it wasn't a new concept then.
I don't disagree - I worked on a task management system many years ago and task and subtask always made a lot more sense than story and task. And epic should just be project.
Had a clueless business analyst get Copilot to write a bunch of stories for an epic, then when she had a meeting with me (and three other people!) to go through the stories I had to tell them that 90% of what they had done was wrong.
If they'd come to me from the outset I could have told them the one story title and handful of acceptance criteria that was required but instead we wasted 5 person hours and whatever Copilot costs.
> let me rewrite this because it’s not a language or framework I am familiar with and fond of
I've been there at least once before and boy was that painful - I already have problems to deal with without someone from another team white-anting us with his ideas (that he doesn't need to maintain).
Yep - I was at a company that replaced something super obscure - I suspect the number of people in Australia that knew the tech was like 10 to 20. The tech was so obscure I don't think there was any path out other than a full rewrite.
A company I worked at decided to rewrite a Fortran system - I suspect that if they wanted to avoid a rewrite they could have started breaking bits off into C and mixing the languages at the linking step... but I understand their desire for a clean break - a rewrite was going to take years but a migration would have taken even longer and been even harder due to the lack of Fortran developers.
I remember reading years ago about some corrupt mod in one of the image subreddits - he or his friend had started some image hosting site and had six different Reddit accounts that he used to upvote posts that used his site and downvote all other posts. It took people a long while to notice what he was up to.
Yeah I'm nearly 15 years into my career and still once or twice a year I have a moment where I think - there is no way that should ever have worked and I really don't know why it ever worked and didn't cause any issues.
Ugh yes. I remember starting on MySQL then being hit by the strictness of Postgres... then terrified by the looseness of MySQL when I moved back (changing jobs).
I remember an old colleague telling me at a previous job they'd moved all business logic into triggers and stored procedures because their database was on their most powerful server. And then one day it wasn't and the database started to choke horrifically.