You should always make sure your code is well-suited for the task at hand. There is no one standard for what is a good way to write code. There is no one way to achieve a certain result.
The best way to make sure your code is correctly written is to do a lot of testing. The more data you have, the more likely it is that there is a problem.
By contrast, the quality of code you find on the internet is generally limited to a few lines of code. So your first task should be to make sure your code complies with the best practices of your technology group and the conventions of the problem domain.
A lot of the time, the code you find in the web is written by non-experts who use the techniques they’ve learned from a particular piece of their codebase to solve a problem with their own code. So it’s important to make sure the code you find doesn’t have the same qualities.
Many of our friends on the internet have been on the Internet for a while. They can be classified as either “experts” or “programmers.” We have seen some people who have worked on the Internet for years on a project that I have written to improve Facebook or Google’s social media and have been at the forefront of it.
We are all experts/programmers or at least have a good working knowledge of what we are.
Of course, I am not saying that programmers should just blindly go in and grab the code and start hacking away at it. Many of our programmers work from home and do not have access to the full source code. However, just knowing what is behind a program can give you a general idea of how it works and what it does. I have learned that it is important to take the time to figure out what is going on in a program and how it works.
Most of the time, the code will be done by humans, so it’s pretty easy to get caught up in it. But for me, there are many reasons to do this.
First, I don’t mind spending the extra time to look deeper at a program, because I am always curious. Second, I am more interested in analyzing the code of a program than just seeing what it does. There are certain aspects of a program that should not be touched, and I hope that someone who is more into computers and coding will take that into consideration.
Just because a program is written in human-readable source code doesn’t mean you can’t analyze the code. You can do a lot of things, but you can’t just look at how the code works and say, “Oh, they’re doing X, and they’re making Y happen. Oh, that’s bad.” It takes a lot more work.
