3 ms·
That's a refreshingly good example of "design by ...cabal..." actually working out pretty well. I think the key element is how the members actually had to imple
by Netcob 6y ago
That's a refreshingly good example of "design by ...cabal..." actually working out pretty well. I think the key element is how the members actually had to implement their designs. If you just come up with a lazy compromise, it'll start haunting you immediately, and not just after the worker bees did their thing.
I think the "cabal" responsible for USB 3.1.1.1.gen2-420gig-whatever should have done the same, with each meeting ending in every member having to explain to their grandma why she can't connect her monitor to her laptop even though the cable fits perfectly, and that it's somehow _both_ the wrong cable and the wrong laptop port.
- danbolt 6y agoI've noticed that happening a lot in my time in the games industry as well. The person making top-down design role isn't exposed to the friction that their decisions are making down the hierarchy. I think the worst part is that they're not even necessarily as invested in the product as someone else, so they're kind of structurally going along with the inefficient situation they're in.