Earlier quoted context omitted.
Not sure if you meant that year literally but I've 1996'd the title for now
Eek, no, I don't know when this was written! :)
Master Foo and the Script Kiddie (2003)
41–44 of 44 posts
Re: Master Foo and the Script Kiddie (2003)
#42It's crazy how cringey "leet speak" looks now. Even words like "woot"
The famous merchandizing website is still alive, but purchased by Bezos, and repurposed into an Amazon dot com "sales" frontpiece.
Re: Master Foo and the Script Kiddie (2003)
#43Earlier quoted context omitted.
These are…abstract. http://catb.org/~esr/writings/unix-koans/two_paths.html Can’t figure out the point
My reading of that is "The unix way is that software should be simple and elegant. The unix way is also that software should work, even if that means pragmatically eschewing elegance and simplicity. You must find a balance between these two things". The last abstract-sounding bit, "When the eagle flies, does it forget that its feet have touched the ground? When the tiger lands upon its prey, does it forget its moment…
So "elegance" and "no bugs" are at odds?
Interesting, that's not my intuition....
Re: Master Foo and the Script Kiddie (2003)
#44Earlier quoted context omitted.
My reading of that is "The unix way is that software should be simple and elegant. The unix way is also that software should work, even if that means pragmatically eschewing elegance and simplicity. You must find a balance between these two things". The last abstract-sounding bit, "When the eagle flies, does it forget that its feet have touched the ground? When the tiger lands upon its prey, does it forget its moment…
So "elegance" and "no bugs" are at odds? Interesting, that's not my intuition....
Elegant code sometimes does not respect the restrictions imposed by reality, such as bandwidth, memory size, I/O speeds, stack sizes, file descriptor limits, user experience, etc.