GitHub Combo 500 Days: make ideal programming a habit

Although there have been 100 days, 200 days, and 365 days of articles, this is not a symbolic 500-day article. For such a thing, everyone will have different views. Some will say this is a good thing, some are not. But it doesn't matter what others think, because you're the only one who knows who you are. Everyone else is just making their point of view.

In these 500 days, I found two interesting things, but also summed up the time to realize:

1. The emotional cycle of programming
2. An intentional exercise.

Well, when we practice constantly, we can write better code.

500-Day Summary

I think you've heard the 10,000-hour genius theory: It takes 10,000 hours to become an expert in a field. Each of these important things is an intentional exercise-not a repetition of the same algorithm in different languages. If we have 8 hours of work per day + 2 hours of improvement, then we still need 1000 days to achieve 10,000 hours.

500 days and 10,000 hours

Of course if you even dream of writing code, then I think 500 days is enough, haha ~ ~.

It's not the most hits, but according to the results of most active GitHub users, it seems to be one of the most committed people in the mainland. Consider the submission is meaningful-not the machine brush out, not consciously to brush, I think there is a great sense of accomplishment.

The two points that are important to achieve a 500-day combo are: time and idea. But I think idea is not very important and we can build wheels, which is one of the things I've done the most in the early days, and I've been building wheels--like the article on making wheels and generating wheels from GitHub. In addition to this, you can use GitHub to manage your idea, and when you think of a plan and the time to complete a thought you will submit it more than once.

Time is a very ironic thing, because people have to work overtime. The reason for working overtime is either because the content of the work is interesting or because of the money. If it wasn't for money, why not go to a different job? such as Division I. There seems to be a lot of confrontation between the two, but I always think that the technology upgrade can solve the problem of income at a later stage, and do not need to rely on overtime to solve this problem. People always want to live, money is necessary, but the programmer's income is not low.

The emotional cycle of programming

Then I observed some interesting phenomena-the emotional cycle of programming is also obvious.

The so-called "emotional cycle" refers to the time of a person's emotional orgasm and the alternating process of low tide.

As shown is the emotional cycle:

Simply put, there is a time period to write code feel super cool, there is a time period do not want to write code , but if a change is: There is a period of time to read books, writing documents feel very cool, there is no need to read, write a document feeling . That's why all the green flowers on my GitHub home page. But because of the internet of Things weekly, I regularly update a related open source project.

But in general, I'm used to making some wheels and creating documents for some time, which is why my GitHub has some open source ebooks.

An intentional exercise.

Programming takes a long time to learn, and it takes a long time to practice. Although I was programmed from primary school, I thought it was a good gift, but it took me three or four years to break through the last hurdle. A large part of the reason is that there is no suitable direction for finding the right one. And during this period there was no good practice, and later in the day I realized that I would encounter the next threshold and began to try to practice consciously.

When I started working, I wrote an article called "Rethinking work." In the article I mentioned a few points of practice:

• Enhanced Code Accuracy
• Write more neat code
• Oral English (foreign company)
• Targeted strengthening of language skills

After some days of practice, I found it was too boring. Naturally like some interesting things, fun is more passionate bar ~ ~. However, the typing exercise is quite interesting:

You can still make a bunch of wrong characters. But compared to the majority of people, it is good, at least blind dozen. However, there is still a lot of room for improvement.

Then I started some of the wrong exercises, like the practice of design patterns and architecture. Try to practice some design patterns that are not available in production, as well as some architectural patterns. And then it means that some design patterns need to be dormitory. Finally, I started the project-based exercise, which is why there are so many reasons for the number of commits on my github.

Predictive Practice

There is also a more interesting exercise, which is a work-oriented exercise. When we foresee that our project requires some technology, we may use certain technologies in the future, and we need to begin to practice these techniques with foresight.

The good thing is: these items may be very popular with beginners in the future.

Summarize

Everyone has their own direction, all have a good development path, sharing and creating is a good way.

The only FAIR are not FAIR. ENJOY CREATE & SHARE.

Please pay attention to my github:https://github.com/phodal.

Forward hold: GitHub combo 500 days: make ideal programming a habit

GitHub Combo 500 Days: make ideal programming a habit