> Maybe it's okay to just throw code out without knowing what it does. I think at time pressure increases, the grey area between right and wrong grows. Here th

> Maybe it's okay to just throw code out without knowing what it does. I think at time pressure increases, the grey area between right and wrong grows. Here the hypothetical user did read the fine manual, and they thought they knew what the code did, and when they ran it, the output was what they expected. Really they did everything correctly, except for the fact that they were wrong. This article is addressing the next level up from RTFM. Given a dev that is reading the manual, how can it be optimised such that they can learn to use the tool correctly? How can project standards be defined so that eg, fiddly date formatting code doesn’t need to be repeated?