3 ms·
Ironically, the quoted description of a pipe wrench seems to be from a patent [1] that's full of references to a picture. And it seems doubly strange to choose
by michaelt 6y ago
Ironically, the quoted description of a pipe wrench seems to be from a patent [1] that's full of references to a picture.
And it seems doubly strange to choose a patent as an example of precisely and uniquely describing an invention in the modern age, when patents are written as broadly and imprecisely as possible.
[1] https://patents.google.com/patent/US126161A/en https://patents.google.com/patent/US126161A/en
- taeric 6y agoYeah, I wasn't at all clear on how that quote helped. From it, I couldn't tell if it was a worm gear, or a screw thread. Nor can I tell how much power the wrench has. Either in torque or in grip. Really, without the picture, I would have no real hint as to what it looked like. Nor how it worked. :( Add to all of that the main decider in regards to strength and build will be material science related, and that description is borderline useless. Seriously, gears don't just cut themselves. Threaded metal fittings are the advanced type theory for these tools.
- taftster 6y agoI think you're right, but that's maybe not giving credit to the overall concept presented. The patent description text, even surrounded with the illustrations, still stands on its own. Yes, a picture paints a thousand words, but it would be nice if software engineers would write their descriptions or documentation as precise as that simple paragraph. So don't miss the point of the article simply because maybe the patent illustration doesn't strictly hold. I'm personally tired of seeing lazy data structures that offer great amount of ambiguity in their use and type. This article hits on a great point that software folks can really stand to improve on.