Bad API Wording, Timed: UNB Put 108 Developers on a Clock and Measured the Confusion
Bad API Wording, Timed: UNB Put 108 Developers on a Clock and Measured the Confusion
A UNB team catalogued 14 ways APIs are worded badly, scanned 4,027 real endpoints — 74 per cent of the REST ones unversioned — then timed 108 developers and watched bad wording triple comprehension time and cut correct answers from 84 per cent to 18.