2 ms·
Doesn't this go contrary to one of the greatest "benefits" of software - that it is reusable? But you are arguing that if someone says, "Just give me the code,
by hermannj314 14y ago
Doesn't this go contrary to one of the greatest "benefits" of software - that it is reusable?
But you are arguing that if someone says, "Just give me the code, I don't care how it works, I have a test and if it passes then I am happy" that this is a bad thing.
What is wrong with that?
"Give a man a fish you feed him for a day, Teach a man to fish and you feed him for a lifetime, but you reduce the efficiency of society since the fixed cost of catching and feeding yourself one fish far exceeds the marginal cost of a fisherman catching one more fish." - American Proverb.
- jdpage 14y agoIn the case presented, the code is, in fact, already written: it's in Cocoa. So all the person needs to learn is how to call that code, which will be generally be different for each application. The reusable bit is already written; they're asking for the specific bit, and they should learn to write that. A library only abstracts the solution the problem; you still have to understand what you want to do to solve the problem at some level, so as to integrate the library into your solution. When someone just asks for code, it is clear that they are not interested in putting in the work to solve the problem; they are interested in getting paid (or getting a good grade, or whatever). I think that one of the reasons that this rubs us the wrong way is because hackerdom, by definition, loves the process of solving the problem, with getting paid being a pleasant side-effect. The person who asks "can I just have the code" is, in many ways, antithetical to the idea of a "hacker".