3 ms·
Of course copying can be good. Code reuse is a good principle. Generally we want people to most efficiently utilize the resources available. Failure to do so
by dasil003 15y ago
Of course copying can be good. Code reuse is a good principle. Generally we want people to most efficiently utilize the resources available. Failure to do so is even dubbed Not-Invented-Here syndrome. Ethics aside whatever you can use to get the job done faster is advantageous.
The problem is that programming is not a cut and paste job. To me the difference between a good programmer and a mere coder is that the programmer has the confidence to solve any problem and debug any issue. Even if you are just doing maintenance work and not working on new features, you need to be able to synthesize and refine an increasingly subtle understanding of the system you are working on. People who don't understand this end when asked to debug something end up just poking at it until they get the output they want. They have no clue whether their "fix" will break 100 other things because they are not forming a proper mental model. I would like to believe that this is inherently obvious to any working programmer, but I can see how it's not if you are under the impression that original work is only done by a few super geniuses, and the vast majority of people in the field are just searching around for something to copy. I certainly have seen this mentality both online in forums, but also in my undergrad CS degree where there were a handful of students who spent extraordinary energy trying to find someone to copy and didn't ever appear to give a rat's ass about any of the material.