2016 year-end summary, new mileage and new start

Reprint Please specify source: http://blog.csdn.net/guolin_blog/article/details/52506273

In a twinkling, a year has passed. According to the habits of previous years, I wrote the year-end summary on the day of December 31, but this year's day is more special, because tomorrow will be a holiday, so I had to write a day earlier this year's annual summary.

Unlike last year, this year I am busy with a lot of things, compared to last year's "Nothing", this year also enriched a lot.

Presumably everyone has guessed that the biggest thing I have been busy this year is to write the second line of code. As I said in my year-end concluding note, I have no plans to write another new book for the time being. Yes, that was actually because I was going to write the second line of code. At the time, I thought that the second line of code was not a new book, but an upgrade to the first line of code.

Before I started writing, I had to identify the directory, and I was thinking of still building on the subject knowledge structure of the first line of code, and then adding the new knowledge in the Android 5.0, 6.0, 7.0 systems, and converting the development tools into Android Studio. The second line of code is positioned to update and upgrade the main, I did not think from the beginning to make drastic changes, because the "first line of code" the original knowledge structure is already very classic.

Unexpectedly, a book I thought was just tinkering, it would cost me so much energy. Although the knowledge structure system and the original is the same, but I can not directly take the "first line of code" of the original, and then where needs to change where to change. So it is very easy to have a large number of omissions, here forget to change there and forget to change, and then the whole book looks like the donkey head is not the horse mouth. Therefore, my way of writing was to write a new book completely in the way of writing "The second line of code", when writing this part of the content, if you can be reused from the "first line of code", then copy it, if not, then write again, this is a kind of I think more scientific writing. However, what you may not be able to understand is that there are few things that can be reused from the first line of code. People who have read this book know that this is a very inclined to the actual practice of the book, every knowledge point is basically the use of the side of the way, so there are a lot of practical examples. But since the development tools in the new book have shifted from Eclipse to Android Studio, the past examples have not been used directly, and the basics need to be rewritten. In addition, from Android 5.0, the system's UI style has changed a lot, so, "the first line of code" hundreds of is also not reusable, all need to re-run on the new system, re-intercept. May be mainly the text part can be reused, but I also can't copy and paste without brain, each copy of the content should be carefully read, see and the new system is not incompatible with the description, should be added some new knowledge of the description.

I started writing this book from February this year, until October, it took about 9 months or so, and it really wasn't much faster than when I wrote the first line of code. Later I saw on the internet there is a comment, this book has more than 90% of the content and the "first line of code" is repeated. I can only say, you can not understand my back to pay the hard, in your opinion may really just copy paste so simple.

Of course, although the original knowledge structure has been retained, but the second line of code is still adding a lot of new content, I am in the old and new, my book, "The second line of code" has been published! This article has been written in detail, it is not here to expand the introduction.

So the busiest thing in a year is here, let's talk about the second busiest thing in the year, running the public number. In fact, my public number in the early 15 when the application, but has not been well run it, at first it was simply to use it as my blog notification tool, every time a new article on the public number to inform everyone. However, this feature is limited in use, so it is registered for almost 1.5 of the time, and the number of concerns is about seven thousand or eight thousand.

In fact, I really want to run this public number with heart, but I really do not have so high capacity, every month I can only write one or two articles, but the good public number is almost daily push.

After a long time of thinking, in May of this year, I switched to a way of thinking, the public number of the use of the mechanism of contributions. That is, the public number of the article does not need to be written by me, or only a small number of articles need to be written by me, most of the articles are from the contributions of netizens, and I will submit articles for review, if the content clearance, will be in the public number on the push. This is for the attention of my public friends, every day can see the quality of the article push, for the contributions of friends, you can get free article promotion opportunities, for me, can be in a low-cost way to operate the public number, so I think this is a kind of co-win mode. Therefore, I also began to use the new model since May has been operating to today, 8 months or so, the number of concerns increased to more than 30,000, but also small results.

Speaking of the public number, I created a public number for entertainment type in the first two months, because I think programmers should not just bury their head in writing code all day, but also have some entertainment spirit, or write the whole nerd. Then I made this public number in order to give you some easy entertainment content, release the usual pressure to write code. Inside every day to push some funny pictures, jokes, sharp turns and other content, are some very short content, a few minutes can be read, the use of work debris time can be a little relaxed. Interested friends scan the following QR code can be concerned about.

In addition to writing books and operating the public number, this year's blog is a good finish. I counted a total of 14 blogs this year, with an average of more than one monthly article. Because usually still have to work, work in addition to write books, operating the public number, blogging and so on, I think this year's blog production is quite good. Of course, next year I will still insist on continuing to write, and share more technical experience with you.

Also to mention my open source framework Litepal, now the use of litepal people are really more and more, and many people have feedback to me, said Litepal more than some of the other database framework useful. Can get everyone's approval, I am actually very happy. This open source framework has been introduced for more than two years, I did not after the introduction of it no longer, but has been maintained in the maintenance, fix all kinds of bugs, to join the proposed new features and so on. This year's Litepal has released a total of 4 releases, and each version has significant improvements in functionality, including support for binary data storage, more than 800% efficiency, support for multi-database capabilities, and more. This open source project I will still continue to maintain the next year, and constantly enrich and improve more features.

Well, this year's end-of-season summary is here. I said earlier that the publication of the first line of code was a milestone in my life, and now the publication of the second line of code is a new milestone in my life. Next year I will embark on a new journey again, there will be new goals waiting for me to achieve, I hope that the next year's end of the summary when I can have more exciting content to write it.

Finally, I wish you all a happy new year in 2017.

Link:

2015 year-end summary, busy and idle

2014 year-end summary, I decided to achieve the three goals

2013 year-end summary, I this year's little bit drops

Follow my technical public number and have high-quality technical articles pushed every day. Pay attention to my entertainment public number, work, study tired time to relax yourself.

Sweep the QR code below to follow:

2016 year-end summary, new mileage and new start