|
Post-secondary schools generally have "cheat checkers" that determine if multiple students copied the same code. That's because each student is expected to learn the material on their own. So in school, discuss things all you want, and feel free to use any combination of other people's ideas - but make sure you write your own code that implements those ideas. It's ok if you generally lean on other's ideas more than your own.
Coding is like anything else - any "new, cool" library or language is a product based on past work with some new ideas, standing on the shoulders of giants as the old saying goes. People commonly make a fork of an existing project - literally copying the whole code base, then alter it as they see fit for their own purposes. People do this because the vision they have is a bit different than the vision of the original project, but the two visions are not compatible - they can't reasonably both be implemented in the same code base.
After grad, if your employer already has some code on some other project that solves your problem, they would absolutely expect you to copy it and use it with as little modification as possible. That's because they want the problem solved quickly, time is more important than everybody deriving their own solution - and that code from the other project is owned by the company anyway.
Hope that clarifies things a bit 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
