3 ms·
As much as it's nice to provide a solution along with evidence that something's broken, it isn't a requirement. Knowing something is broken is a different skill
by aaron-santos 5y ago
As much as it's nice to provide a solution along with evidence that something's broken, it isn't a requirement. Knowing something is broken is a different skill than fixing it. It's the reason we have mechanics, doctors, and QA to name a few. I'm willing to bet there are much more socio-political creative types that can imagine systems much better than I can. After all, I'm just a layperson in that domain. Challenging lay people is exactly as absurd as challenging them to come up with a fix for their join pain before consulting a doctor.
- munificent 5y ago> Knowing something is broken is a different skill than fixing it. This is a fair point. But I think many people saying "the system is broken" implicitly or explicitly advocate a fix by throwing out the entire system. Those people often don't seem to realize that "no system" is a system too, and you need to compare that system's emergent behavior to the current system before you can make a wise choice.
- AlbertCory 5y agoExactly. It's fair to propose minor tweaks to a system while (implicitly) admitting that it's fine otherwise. It's quite something else to say "the system is broken" while having no idea whatsoever how some new system would avoid all those problems.
- AlbertCory 5y agoNo, actually, it isn't. It's more like "I assert that my joint was badly designed by evolution and a competent human could make it better" without having any actual ideas how it might be better. Your examples are also flawed. Mechanics and doctors fix one instance of a system. They are not charged with fixing all of them.
- aaron-santos 5y agoOk, car designers, and bio medical engineers then. Hope that makes more sense for you.