3 ms·
As software evolves and gets more complicated it only makes sense that bugs will become more obscure and tougher to chase down in projects that are reaching siz
by nanodano 10y ago
As software evolves and gets more complicated it only makes sense that bugs will become more obscure and tougher to chase down in projects that are reaching sizes we've never seen before. Most developers have a bug list longer than they can handle. It's not about 'giving up' it's about prioritizing. It's not about being lazy it's about only having so much time in a day.
- deleted 10y ago[deleted]
- tracker1 10y agoStart 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 10y agoWe do this. What next?
- tracker1 10y 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.