3 ms·
Amusing, but this is where engineering thought differs: obviously your rediscovery of the 5:12:13 right triangle or whatever was precocious and showed a deeper
by ajross 15y ago
Amusing, but this is where engineering thought differs: obviously your rediscovery of the 5:12:13 right triangle or whatever was precocious and showed a deeper mastery of the subject.
That said: your advice sucked. The 3:4:5 triangle is a better choice for obvious reasons (smaller numbers) and not so obvious ones (less sensitivity to measurement error due to larger internal angles).
The critically important distinction there is precisely that between, say, Haskell and Ruby. :)
- derleth 15y agoExcept both Haskell and Ruby are useful.
- bryanlarsen 15y agoActually I couldn't even get him to agree that a 6:8:10 triangle was equivalent to a 3:4:5 triangle.
- madhadron 15y ago> The critically important distinction there is precisely that between, say, Haskell and Ruby. :) Absolutely. Why bother with all that unnecessary complexity in Ruby?
- ajross 15y agoI know that was sarcasm (as was my original post), but that's kind of my point. Haskell is a simpler language than Ruby in a lot of ways. But the extra complexity in Ruby (or Perl, whatever -- pick your workaday language) is driven by clear practical concerns. Where a functional nut would sit and worry about getting a design right that correctly abstracts the properties of any right triangle, a web developer is happy to hard code the values for 3:4:5 because that's all that's required. And he isn't wrong to do so.
- fpgeek 15y agoPerhaps, but he isn't necessarily right to do so either. If the requirements for the triangle are uncertain enough or change often enough taking the time to get the abstraction right can be appropriate engineering tradeoff.