Is it bad to use other peoples code?
Originally Answered: Is it bad to take other people’s code? Definitely NO. As a programmer, you get bonus points anytime you re-use someones code, because it’s already written, so you don’t have to waste the time to think of an algorithm, write it, and implement it.
How do I get better at reading other peoples code?
How to Read Code (Eight Things to Remember)
- Learn to Dig. When you’re diving into a mature codebase for the first time, you might not feel like a developer.
- Go Back in Time.
- Read the Specs.
- Think of Comments as Hints.
- Find Main.
- Notice Style.
- Expect to Find Garbage.
- Don’t Get Lost.
Is reading others code good?
It’s a wonderfully self-perpetuating cycle: you read more code; you gain the ability to understand it quicker and more effectively; so you are able to consume even more code; and so on. And it doesn’t stop there: you’ll also see huge positive gains in your own coding.
How long does it take to get good at coding?
About 3 – 6 Months. With passion and focus, an hour or two a day can go a long way over the course of several months. Whether it’s through programs like our After-Hours Bootcamp, or utilizing online resources, it’s very possible to find a way to balance coding with your busy schedule.
Is it good to read other people’s code?
Reading other people’s code is an opportunity to get to know someone else through their code. We all express ourselves through our programs. For fun, I’d recommend you pick someone you admire and get to know them through their work. A big part of this process is accepting people (and their code) as they are.
How do you go about understanding others’code?
Use a white board to write out and diagram interactions between classes or methods. This can help you to see the flow of the program. Once you have the 100ft view, then start digging, tracing and debugging to find the nuances of the system. Generate/draw/read a call graph.
Can you understand other people’s code without judgment?
If your thoughts automatically went to code reviews when reading the title, you are not alone. However, this post is not about code reviews, quite the opposite. I’m going to ask you to approach other people’s code without judgment, with the purpose of understanding, not evaluating. It might surprise you how difficult this is.
When to write documentation for other people’s code?
You might then turn to the lack of documentation (it’s funny how most programmers find documenting their own code to be a chore, but can be furious at the lack of documentation of other people’s code). Learning a code base or a module is, however, the perfect time to write documentation.