[pbhjpbhj]

Not a dev: " Twice daily deploys don’t happen if QA goes through a 48 hour test process".

Why does that matter, surely it's pipelined. If you feed in RC packages to a 48h QA twice daily then after 2 days lag you're getting tested code twice daily.

I'm not suggesting that's realistic for large software houses, just that the logic seems wrong?

[simonbw]

I think the QA process isn't usually as pipelineable as you're suggesting. On a website it's often easy to QA changes that happen on page A at the same time you QA changes on page B. But in a game, especially one like factorio, it's probably a lot harder to find features that can be tested and deployed simultaneously with other features.

It would be easy to test changes to the design of Level 3 at the same time as changes to the design of Level 5, but it would be hard to test changes to the way inserters work at the same time as testing changes to the way conveyor belts work.

[bombcar]

If the QA cycle is too long the developer gets out of the zone in that area - two days isn’t bad but some places you won’t get review or reports for weeks after submitting code.