3 ms·
If you need nuanced behavior, you need a complex controller. And you always need more nuanced behavior, this is the inherent nature of software development. Som
by Mikhail_Edoshin 3y ago
If you need nuanced behavior, you need a complex controller. And you always need more nuanced behavior, this is the inherent nature of software development. Sometimes the appearance of simplicity is achieved by making the behavior simpler (e.g. dropping the support for old versions, not implementing parts of the specification, and so on). This is degradation, not simplicity. The right simplicity is an art of having the required complexity yet somehow manage it internally. So complexity is not bad. It is given. What is deficient is our skill.
- Spivak 3y agoi don't think grug actually disagrees with you here but takes the position that skill both can't be counted on and doesn't scale. And this matches my own dev experience cathedrals of complexity pale into comparison that code that's easy to throw away and rewrite to meet changing requirements or scope.
- harimau777 3y agoMy experience has been that the powers that be generally won't give developers time to rewrite to meet changes in the requirements. Personally as I see it: iterative development with time to rewrite > cathedral development > "iterative" development without time to rewrite I think that most teams actually do "iterative development without time to rewrite" so cathedrals of complexity would actually be an improvement.