4 ms·
"dude. i know that's not what it's supposed to do, but actually it's better. it's a feature, not a bug. no, no. it's not shitty, and no i'm not refactoring it a
by a-dub 5y ago
"dude. i know that's not what it's supposed to do, but actually it's better. it's a feature, not a bug. no, no. it's not shitty, and no i'm not refactoring it and neither are you. it works better and they'll never be able to fire us. it's like jane jacobs and shit. leave it alone. the bits are happy."
- snapcaster 5y agohaha, great comment. This whole thread is full of people who enjoyed Seeing Like a State loving the discussion
- shoo 5y agothis module is a thriving, multi-use community of interacting concerns and responsibilities. yes, it would be more legible to central administrators like us if we evicted all the requirements and implementation details, paved it over, then redeveloped it into a high modernist Corbusian hexagonal microservices architecture. but truly, who would want to live or work inside such a bleak module structure, where instead of simply nipping downstairs to share surplus resources with unrelated business logic in the parent stack frame, you would have to traverse through endless tiers of serialization, transit, deserialization & be subjected to endless authoritarian checkpoints for authorisation by central authorities?