3 ms·
I think your thesis is better posited as Complexity != Complicatedness i.e. a complex system can be uncomplicated (eg. iPhone), and a simplex system can become
by bobosha 4y ago
I think your thesis is better posited as Complexity != Complicatedness i.e. a complex system can be uncomplicated (eg. iPhone), and a simplex system can become very complicated (eg. the US tax code).
IMHO Complexity is a function of the number of subsystems; while complicatedness is the function of the nature of those interactions.
- OJFord 4y agoI have that feeling a lot in ticket complexity estimations - something needing to be done in a tonne of places for example doesn't make it complex: it can be trivial and yet tedious, long, and time-consuming. (Which leads straight back to the worst part of it - why do we pretend complexity is what we want to estimate anyway? We all know it's time the managers at least are interested in. We don't have 'an appetite' for x amount of complexity in a two week period, we have time for a certain amount of stuff. Calling it complexity is just pretending not to be micro-managing time; we should estimate time (and call it that) but have an expectation that the estimates will often be way off and a culture that that's fine.)