3 ms·
Start with very small, modular code... avoid spaghetti coupling (that is removed by multiple laters)... organize structure by feature, not type/class, and accep
by tracker1 11y ago
Start with very small, modular code... avoid spaghetti coupling (that is removed by multiple laters)... organize structure by feature, not type/class, and accept that all features don't look the same... Some features may only be data structures, service libraries and/or ui.
Separate event chains from your UI so much as practical, and avoid classes that look like Car, Wheel, etc that are too smart for their own good.
- jschwartzi 11y agoWe do this. What next?
- tracker1 11y agoActual code reviews, experienced architect(s) that actually understand the whole project, and paired development. Not being afraid to refactor... creating componentized pieces that can live in separate codebases if possible.