Remix.run Logo
▲ jon128 5 hours ago

If the technicians in the Framework support center say the two keyboards they tested were working perfectly, they obviously were working perfectly.

The other keyboard, the one the customer already had, was the one that was obviously not working perfectly.

_

> if a customer complains about a keyboard issue that we can't reproduce, we replace the keyboard anyway.

The obvious thing to do. Not doing this is the mistake Framework made.

_

> shouldn't have to pay for the replacement part out of pocket, that's literally the entire point of a warranty.

An in ideal world, no one should have to do anything.

From a logistical standpoint, competent people know how to make results happen. As someone operating in a business I would order a new keyboard.

Could just send the entire laptop back.

_

What I can say for sure, when I have had to make sure that developers and other users are operational, not a single person went with more than a day of downtime just because one (or even two or three) laptops had issues.

Framework is awesome. I am personally responsible for more than one dozen of Frameworks being deployed and will probably be responsible for many more.

▲phendrenad2 4 hours ago | parent [-]

> If the technicians in the Framework support center say the two keyboards they tested were working perfectly, they obviously were working perfectly.

Ah no, that is not "obvious". It's entirely possible that they put the keyboards into a test harness that didn't actually test the things that were reported broken (module appearing as a numpad, c key inserting a backspace), and the technicians were not trained or allowed to go outside the testing parameters.