I’d like to wish you all a happy New Year and wish you all a better and better year in 2018.

Think to think, learn luo fat, or use knowledge to cross the New Year, a few more cool.

On the last day of 2017, let’s take a look back at personal technology growth and make a few predictions about what’s next. Make a summary for yourself, if it’s helpful to everyone, so much the better.

Back in 2017

Since I co-founded a small start-up company in April 2016, I have paid less attention to specific code writing. 2017 was no exception, and my main work focused on the following aspects.

  1. Standardize the project development process, mainly with framework code, or code wiki.
  2. Marketing, product and other non-technical work.
  3. Spare time to study some cutting-edge technology work.

Mainly reflected in:

First, the rails-Template fix, in addition to the latest Version of Rails, added CDN configuration guidance, Monit automatic monitoring code, automatic log splitting, exception notification, SSL configuration code guidance, and data backup.

In this way, we can guarantee almost 99% reliability and almost zero cost maintenance for any project. It’s been iterating for two years now, and I think I’ll keep tinkering.

Second, I facilitated the implementation of mobx technology in the process of developing memeapps, a data-driven library for cross-page communication of memeapps that can help teams accomplish complex memeapps more elegantly.

The third, react-Native template-Mobx refactoring, is also a scaffolding project for the integration of React Native and MOBx. In the middle of this year, We saw that React-Native started supporting templating technology. Refactoring to a command generation project framework. This project almost buried our React Native process. However, the team has been mostly focused on applets recently, and the project has not been updated more closely with React Native.

I also studied the technical principles of Mobx in depth, formulated a Mobx-Ruby project, wrote some basic code, and shared it in RubyConf China in 2017.

All three are open sourced on Github and can be found at github.com/windy.

In the past two years, I have obviously felt the rapid development of front-end technology direction and industry changes, such as the rapid development of Vue of You Xiaoyou and the rapid development of JS framework of full stack of Meteor. React was introduced and Mobx was on the rise.

Let me make a quick prediction for 2018.

Tech predictions for 2018

Vue will continue to grow rapidly. I prefer the framework of actual efficiency improvement. Vue’s incremental framework has been well accepted by people. Although there is no big company behind the endorsement, you xiaorighty’s community operation is very good.

There will be more development of front-end Reactive Program technology, such as MOBx, RxJS, CycleJS and even RxJava in the Java community that I don’t pay much attention to.

Full-stack frameworks such as Rails maintain a stable user base without much impact from new technologies, and over time NodeJS, Python, and PHP remain relatively stable as well. I think the reason is that they can’t pull apart an order of magnitude in terms of development efficiency.

Go, Rust will both have a good run, while Swift will have a tough one. This is the feeling from the market demand.

The above is a personal judgment, mainly years of experience summary and market feelings, for everyone to refer to the growth of the year, do the right direction can get twice the result with half the effort.

In addition, I also want to sum up the technical growth process skills, mutual encouragement.

Never be satisfied with the status quo

When I first came to Shenzhen in 2009, I was a trainee software test engineer with only “50000 code” experience. I never thought that today, I could run a small start-up company and support a team of about 10 people. That’s orders of magnitude less than the teams that raised tens of millions of dollars in 2 years, but far more than they thought at the time.)

For myself, the most important rule is never to be satisfied.

Not satisfied with the status quo, so that they can continue to read after zero; Not satisfied with the status quo, let oneself constantly break through their own technical boundaries, from testing to automated testing, from automated testing to quality technology manager, to the back of the independent business; Not content with the status quo, pushing yourself out of your technological comfort zone, trying to understand the social economy, understand cutting-edge developments in physics, and understand the inner workings of business.

But I would add to myself that sometimes you can do too much of a good thing. Pay attention to the process and drive yourself with interest.

Extremely open

It’s easy for us tech people to be self-righteous, and I’m one of those people who always feel that what we understand is right. This is what technology goes through. They don’t accept other people’s ideas easily and are skeptical of them.

However, as you grow up to a certain point, be extremely open and put yourself in the “God” perspective to see what technologies look like that you would never touch before, and what are their problems and advantages. In short, keep trying to fit your thinking into the larger society without creating internal conflict.

Because of this principle, I went from being a full-stack Rails advocate to being a true evangelist for AngularJS front-end separation, and back to the practical Rails full-stack + Webpack path.

Not just open, but extremely open.

In life, I say to myself, 18 years, to be extremely open, to try to understand everyone’s logic, to analyze why they are formed and whether there are holes in it.

In conclusion, I am a pragmatic and somewhat idealistic technical person.

Practice is king

Confucius said: learning without thought is useless; thought without learning is perilous. Wang Yangming said, knowledge and action are one.

The more I experience, the more I realize the importance of these basic principles.

For example, it is only by practicing the separation of the front and back ends that you can understand whether the strengths and weaknesses of others exist and be more profound than others. Only by doing it yourself can you really know whether “Starting a Business is hard” or not.

Now, I realize more and more that there are only a few basic truths (principles) in life, and the rest are derivative products, who is not bad depends on who feels more deeply.

First dig a base on the skills, and then lateral expansion of their own ability, is our deep wave family magic weapon.