3 ms·

So a the goal is a bunch of people can have their claws in the code base and avoid this reaction [0], but not necessarily code optimization, just as long as eve

So a the goal is a bunch of people can have their claws in the code base and avoid this reaction [0], but not necessarily code optimization, just as long as everything is highly modular and works independently of other parts you're kosher. [0] https://www.youtube.com/watch?v=BGpDGJoe6P0 https://www.youtube.com/watch?v=BGpDGJoe6P0

jaggederest 9y ago
Right, the lower level stuff you're still looking for (cleanly designed classes and methods, good testing, etc), but you can hit all those micro-level targets without having any architecture to speak of. (the "pile of classes" design pattern, where everything calls everything else and there's no hierarchy or anisotropy to it) The other heuristic, besides "names make sense", is ease of modification. When you come back into an area of the system, how painful is it to disentangle that piece from the rest and make a significant change? Is the functioning of the entire system tied together tightly enough to make that difficult? Are there good patterns to extend, or is every change invented from scratch?