4 ms·
We have a print-out of an N-set Venn diagram on the wall which we use to illustrate the peril of having too many features with subtle interactions. It resonate
by megrimlock 14y ago
We have a print-out of an N-set Venn diagram on the wall which we use to illustrate the peril of having too many features with subtle interactions. It resonates because many of us have worked on areas of the code preceded by comments indicating which subset of interacting features you need to keep in mind. There's at least 7 such features, so it's not a small space. We've been desperately struggling to make these features more orthogonal and having a succinct diagram of the problem (read: "enemy") has helped us stay motivated.
- lwat 14y agowat
- walrus 14y agomegrimlock has a poster of a Venn diagram on the wall. The intersections in the diagram represent interdependencies between different parts of a piece of software (in object-oriented programming terms: places where encapsulation is broken). The Venn diagram is there to motivate the removal of those interdependencies.