What is the essence of programmers learning projects and code?

It's easy to learn things. It's hard to be yourself.

Novice programmers find themselves stealing ideas from other projects in several recent projects. Of course, it's not really stealing, it's about browsing and learning the projects and developers you admire and stealing ideas from them. such as design patterns, refactoring methods, and so on. How does Chris handle command-line parameters in the hub? How does the RVM of the shell script and Ruby perform Wayne conversions?

When you have a problem, a bit of difficulty, and you need to move your brain, you have to ask, "Hey, how do I achieve this?" "That's a good question to start with," he points out.

Once you encounter this kind of problem, of course, you can take the ding-ting academy Learn more it knowledge and find solutions. But if you steal from someone, you will reap two points:

There is an ideological connection between your understanding and that particular project.

You "own" that thought.

"Owning" What you stole is a subtle process, but you can imagine that you spend a lot of time understanding these ideas and you apply them to solve your own problems. The process of thinking is very satisfying. Suddenly, you start to understand why the authors want to refactor this method and why they need an auxiliary class.

Do not misunderstand; it is of course best to be able to create things by yourself. This is where learning knowledge reaches an entirely different level, which in most cases requires us. But sometimes learning good experiences from others is one of the quickest ways to enlighten-not to solve the problems you have at hand, but to essentially understand the essence.

Observe how other people solve your problems, to understand the ideas embodied in them, to re-shape it in your own opinion, to make this thought "your" thought, and you put it in your head for the next project to be used. This is another term for the word "learning", but just when I think of this imaginary, strange statement--Oh, that's the inheritance strategy I stole from homebrew a few months ago in another project--my ability to accept knowledge has improved.

Once your assimilation of knowledge reaches this level, then these inward thoughts become your own thoughts that twist in your mind. Of course, if you feel that your knowledge level is not enough, you can go to the ding-ting Academy and other professional platform to continue to exchange learning. In short, we must constantly study and think.

What is the essence of programmers learning projects and code?