3 ms·
...those of us who design and write software find that our approaches are relatively orderly but fragile. Aspects of a system fail to support each other, and we
by contingencies 12y ago
...those of us who design and write software find that our approaches are relatively orderly but fragile. Aspects of a system fail to support each other, and we basically add complexity to the system in order to hold it together. Highly engineered systems are thus brittle
Honestly? I am more likely to conclude that the author is not yet very mature as a programmer.
- vonmoltke 12y agoOr has a distorted view of what "engineered systems" are.
- Glyptodon 12y agoRather prideful response there. Most systems I've ever worked with (I end up working on existing systems much more than implementing from scratch) are brittle somewhere in the sense of being potentially incompatible with some random enhancement X sans major rewrites. And when major rewrites aren't possible we resort to complexity. As developers we're all aware of this and often refer to it as managing technical debt, no?
- contingencies 12y agoI was aware this could come across the that way when posting and am no paragon of perfection, but that doesn't change my perception. Technical debt is technical debt, and a brittle and complex system that evolves as a patchwork is just an admission of software development driven by bad process.