> but please seek feedback and advice on crucial design decisions.
Or at least isolate them from the rest of the code. Of course, it's difficult to recognize which design decisions are crucial without already being an expert, so this sort of advice is probably silly. It's probably also the kind of advice that would have been more likely to strangle Anki in its crib rather than giving us the opportunity to discuss how a wildly successful program that has helped many people learn many things should improve its data model.
I'm not saying they need an expert or they shouldn't push forward anyway, but it's good to recognize when you're out of your depth and to get input when possible. There's a lot of value from just running something by someone else to see if they can understand it and if something occurs to them that would make things simpler.
Or at least isolate them from the rest of the code. Of course, it's difficult to recognize which design decisions are crucial without already being an expert, so this sort of advice is probably silly. It's probably also the kind of advice that would have been more likely to strangle Anki in its crib rather than giving us the opportunity to discuss how a wildly successful program that has helped many people learn many things should improve its data model.