Summary of my 2016 and planning my 2017 | the nuggets technical essay

My 2016

2016 is a fruitful year for me. In 2016, I really set foot on the path of programming. From the first time to write 2000 lines of command line C language version of “JINGdong Shopping Management System”, to follow the senior of grade 14 into the pit of Android development. From C to Java to C++. From the discovery of Github to the establishment of static blog, from the completion of the first Android project with my senior to the independent development of the front and back end of Android. I was satisfied with my year. Instead of feeling sorry for myself, I actively shielded myself from external influences. My ability to solve problems has also been greatly improved, and I can solve most of the problems in programming by myself. To sum up my 2016, I can be divided into the following points:

• Getting started with videos works best when you don’t know anything. Because I’ve found that reading books slows down progress and undermines confidence if one doesn’t know anything about a particular area of programming. Videos, especially on MOOCs, tend to be aimed at people with a zero-dev base and can be a quick start. When you walk in the door, don’t watch the video, it’s the stuff in the book and you can always dig into it, and it takes an hour or two to do a couple of chapters in the book.

• Face up to your English limitations. Many people may take a glance at an English document when they first start reading it and then stop reading it if they don’t understand it. When I was learning Android, I found that the English documentation of Android is very detailed, and the inheritance relationship of each class is clearly listed. At first glance, it seems that you can’t understand anything. In fact, if you look it up carefully, you can still understand it if you look it up in an electronic dictionary.

• Be sure to practice. I think programming is a discipline where practice trumps theory (except perhaps algorithms). If you just read without writing code, I’m afraid you can’t really understand. I was very impressed when I learned Android. At the beginning of learning the four components, I was thinking about this thing, so I looked at it again and again, like doing math problems in high school to understand it on paper, the result is still not very good. I didn’t know and remember how to use it until I wrote the Demo myself.

• Don’t be afraid of the unknown. When I applied for the open experiment project of the school, I thought that the APP function I made was too simple and could not be displayed on the table, so I took the initiative to add the back end in the function introduction of the project proposal. In fact, AT that time, I did not understand the server and network, I did feel a little panic, in case it could not be realized. I searched the web for server-side knowledge paths and learned that Python+Flask is a lightweight framework that works best for my APP. So without a word, I started learning Python and Flask. It took less than a month to set up the APP server. What I learned from this is that programming is often not as hard or as easy as you think.

Outlook 2017,