2017 list required by front-end developers

As front-end ecosystems develop rapidly, we spend time trying new technologies and discussing them online. As front-end ecosystems develop rapidly, we spend time trying new technologies and discussing them online. I don't mean it shouldn't be the case, but maybe we can slow down and pay more attention to things that haven't changed much. These things can greatly improve the quality of work, increase the value of work, and help us understand new tools.

In this article, I have my past experiences and plans for the New Year. I also hope to receive your feedback.

Learn how to write readable code

Most of our work is not to write new code, but to maintain existing code. This means that you read code much more time than code writing. Therefore, you need to optimize the code for your next colleague who maintains the Code, rather than for the interpreter.

I recommend that you read these great books from thin to thick in the following order:

The author of the art of writing readable code is Dustin bostin

Author: Robert C. Martin

The author of code Daquan is Steve McConnell.

Learn more about JavaScript

Almost every week, a new JavaScript framework is better than the old one, which makes it easy for us to spend most of our time learning the new framework rather than ourselves. If you are using a framework but do not know how it runs, stop and start learning the language until you understand how the framework runs.

You 'd better start with Kyle Simpson's "JavaScript You Don't Know" series, or read it online for free.

Eric Elliott made a big clear order for the JavaScript theme you need to learn in 2017.

Henrique Alves also provides a list of knowledge required before using React (actually any framework ).

JavaScript Developers: Watch Your Language author Mike Pennisi done, can understand the TC-39 to add new features of ECMAScript process.

Learning functional programming

We always want JavaScript to have classes. Now we finally have it, but we don't want to use it at all. function is what we want most! We even use functions to write HTML (JSX ).

Functional-Light JavaScript by Kyle Simpson.

Professor Frisby's book Mostly adequate guide to functional programming and free courses.

Learn Basic Design Knowledge

As front-end developers, we are closer to users than anyone in our team, or even designers. When the designer has to check each pixel on your page, it means you have made a mistake.

Design for Hackers: Books and free courses.

Design for Non-Designers, Tracy Osborn.

Design of Web Applications, Nathan Barry.

On Web Typography, Jason Santa Maria.

The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity, Alan Cooper.

A few articles on animation in UI: How to Use animations to improve user experience and interface transition effect.

Learning to cooperate with others

Many of us choose programming because they want to communicate with computers rather than people, but unfortunately this doesn't work.

We rarely work independently at ordinary times: most of the time we have to communicate with other developers, designers, product managers, and sometimes users. Although difficult, if you really want to know what you are doing and why you are doing this, it is very important. After all, this is the value of our work.

Soft Skills: programmer survival manual, John Sonmez.

Programmer's professionalism, Robert C. Martin.

From scratch, Jim Camp.

Learn to write for others

Most of our daily communication with colleagues and others is textual: task description and comments, code comments, Git commit information, chat information, emails, and tweets blog articles.

Imagine how much time people need to read and understand the content. If you can reduce the time consumption by writing more clearly and concisely, the working atmosphere will certainly become better.

William Zinsser.

Elements of Style, William Strunk and E. B. White.

Orwell's writing law.

There are great Glavred courses in Russia.

Learning traditional computer science knowledge

Front-end development is no longer a simple drop-down menu animation. Its complexity has reached an unprecedented level. As the problems solved by the front-end become more and more complex, it is inevitable that there will be a "JavaScript fatigue"

Therefore, we need to learn the computer science knowledge accumulated by non-front-end developers over the past few decades. At the same time, I hope to hear your suggestions.