Writing code is also very important and should be taught in CS school. As stupid as it sounds, but the best way might be in the middle. Giving tasks to create c

Writing code is also very important and should be taught in CS school. As stupid as it sounds, but the best way might be in the middle. Giving tasks to create code and also giving task to reuse and change code. That is how our teachers try to teach us and I feel acceptably comfortable in both situations, writing a new program as well as moving around in other peoples code. One thing I want to add: The really bad thing about these "reusing" students is, that they have no skill to see which code to reuse. Most code you find with google is just duct taped itself. And trying to solve any problem with ducttaping an already ducttaped monster is ridiculous. What I saw in my undergrad classes from my classmates was so bad to read and use, that I decided for myself to write a lot by myself and don't rely on others. That got so far, that in one project I wrote my own linked list instead of using the Java's basic one. Of course that is a little too far, but makes for a small, funny story. I'm still not a really big fan of reusage, because design and engineering is something that is treated to lighthearted by many many coders out there. Until you are finished analysing all the options, you often have constructed your own solution and learned more about the innards on the way.