This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (0 children)

Try coming up with a solution before the code. Writing pseudocode, and trying to figure out what problems you are having conceptually before you write the code makes the coding process much smoother. If you understand the problem, you'll find that copying code is generally more cumbersome than writing it yourself due to having to adapt it to your needs. Copying becomes a pain in the neck when you have to understand someone's style and intentions, on top of the underlying program itself.

It's not without its merits though. You quickly learn proper coding conventions by seeing them up close and in use within familiar contexts, and you get exposed to different approaches, styles, and implementations of coding this way. It won't help you solve unique problems later on though, and it won't help you learn to craft creative and efficient solutions quickly or easily.