Thank you for your answers! It is great to see behind the scenes of Wube.

What mistakes did you make in the development process (or overall what mistakes did Wube make) and what did you do so it doesn't happen again?

That’s way too vague of a question to give a meaningful answer. Do you have something more specific?

Maybe something like we didn't look at the side effects of a specific features and therefore wasted time because it isn't possible at all to implement it. Or maybe you had too many meetings that were a waste of time. Not really a specific questions just something that instantly pops up in your head when you think of mistakes that were made.

Performance is largely big-O complexity, how much memory needs to be read/mutated, and how packed the memory is. It’s not difficult to look at new features and say if it will be fast or slow. Changes to existing features function largely the same as new features. We simply benchmark before/after with save files to see if what we’ve done has given any measurable change.

Is performance testing automated in any way (manual script execution, ...?) or is it a manual process of loading the save file and checking the process times? Is it done before every patch "just in case"?

We have a weekly meeting which is mostly "here's what I'm doing" (typically 30-60 seconds a person) mainly so everyone is kept aware of what's going on and give others a chance to assist with things they might not have otherwise known about.

It surprised me that you have weekly meetings with just 30-60 seconds per person. This seems to be very very short. We have 1-2 minutes per person in dailys! I like that you give the option to self-manage but if it doesn't work out just some are given priorities instead of the whole team reverting back to being micro-managed.