4 ms·
On the other hand, you have redundant systems where everything seems fine even if some parts are not working. If you don't have good monitoring, you won't notic
by skybrian 8y ago
On the other hand, you have redundant systems where everything seems fine even if some parts are not working. If you don't have good monitoring, you won't notice when you break something until other things break as well. Or maybe it doesn't stop working and you just have mysterious brownouts or irreproducible bugs?
Generally speaking, programming is easier when you have clear feedback. Things either work or they don't, and you don't have to do a lot of expensive testing to gather statistics to show there's a bug.
- erikpukinskis 8y agoI wouldn't say that redundancy is the alternative to brittleness. The altnernative is smaller code, less tightly coupled, that uses fewer libraries and more beginner level language constructs. There's no technical impediment to that. It's actually less work technically. It's just hard to design that way, because you have to actually understand your domain much more deeply. That's where stability comes from, not redundancy but the opposite of that. Fewer parts, better understood.
- skybrian 8y agoIn a minimalist design, everything has a purpose, so if you remove it, it breaks. That seems good. And yet, brittleness is supposed to be bad. How is it different?
- erikpukinskis 8y agoI would say minimal means something like "just enough flexibility to support one stated use in all predictable contexts". Brittle means "not enough flexibility, so it breaks in some contexts". Removing a component is not a stated use. If a component can be removed during the stated use then that's not minimal, it needs more thought or parts.