Three thought _php tutorials that front-end engineers should have

Three ideas that front-end engineers should have

Editor's note: This article through logical thinking, business thinking, design thinking of three dimensions to match whether you are a qualified front-end engineer. Because front-end engineers are not just responsible for receiving information, data, and responses to these chores, they should be more required to communicate with back-end engineers, design, PM. So, teamwork, co-ordination, and so on need to take into account more things than the code.

If you are a genius engineer can leave at once and can do a lot of things independently, you can be a geek because I believe no one will not admire you. But reality is reality, most people are not geniuses, and we are not alone in the workplace, we need teamwork, need coordination and cooperation, need to consider more than the code of things.

Front-end engineers are not just responsible for picking up data and making a response. Of course, it is not wrong to do this, but we need to communicate with the back-end engineers, we also need and design communication, but also need to communicate with PM, how to do the three parties are more beneficial?

Logical thinking

When you start writing a piece of code, think about where it will be used, and reuse it? Will it change later, if it changes, how can it change? The general structure of the Web page changes, although there are a lot but there is a basis, the basis is can be pre-estimated good. No case, is not "do not change", many times you have to do one side of the change, and may even come to a big diversion. What do you do when there is a need for change and modification? These are all needed to be well thought out and built on a logic.

Usually professional designers, the design of a Web page elements are homogeneous high, and so on or contrast, so the code is logically also can be reused. So why do you learn to use CSS preprocessor (sass,stylus,less), write a Mixin or a variable, start with you will feel very troublesome, but use you will not go back, not only improve your efficiency but also improve your accuracy rate.

The world of engineers, such as martial arts, we all have their own cultivation, every day has a new secret, we are very curious to run to cultivate a bit, hope to become a martial arts master. This is also to enhance your insight and professional motivation, if you do not have the curiosity, to see and to know too little, logic naturally will not keep up with the times. To maintain continuous learning, to hone their logical thinking.

Logical thinking to a certain extent, is your program professional ability, in addition to write to also can be maintained, can read. When things are based on a good logic, the odds of error are lower and the people you work with are happier.

Can do one thing well, that is master, can do one thing well and predict the future, that is the experts.

Business Thinking

PM, boss or customer, will ask you, "How much time do you need", if said too short, may do not finish, if said too long, also impossible, this is a question how to answer how to die. Sometimes it takes a different stance to think in terms of a third party. Our degree of completion may not be the same as their degree of completion.

We divide the details of the case into two cases, one that you have experienced and can estimate time for, one that you have not done or that you are unfamiliar with, and you have no time to estimate the basis.

So propose a standard that they can accept at least, such as an app site, a minimum standard that requires a home page, and a link to download the APP's 2 buttons, which are all predictable. And the rest, you need to study, and then give a more based on the time. It's very, very important to estimate how much time it takes to finish a case, because you're consuming a group of people's time, not your own unless you do it yourself, or you're the boss. If you estimate wrong, the back will be postponed, do not have a big relationship, the most important thing is to solve the problem, put forward your solution, what kind of method can achieve the purpose of solving the problem.

Change a position to propose the solution, to the thing is helpful, to the company or the customer is helpful, the customer does not care that you can not solve the mobile phone page can not see 20 columns of the table that problem, but the customer is happy to hear you say, this table is not good to see, you can change a display method. Customers don't really care if you're using Rails or PHP, and they pretend they know it, and they can shop and dispatch.

Front-end engineers may have easy access to customer complaints, so some things are not well thought out and will be troublesome. Do a Web site, in exchange for you are users or customers, you will be satisfied with your own site to do?

Design Thinking

Many times, front-end engineers themselves are also designers, but there are many are itself front-end engineers are also back-end engineers, design and front-end is inseparable. Of course I'm talking about the design, not really want you to get a picture or a complete design.

It's not just about it looks like and feels like. Design is how it works. -steve Jobs

The front-end design refers to a picture or element, how to be executed and created, moved or eliminated, this design in different widths and heights, different devices to see, the effect is how, consider it is your design thinking, how to put the designer's picture into a living page, to use the designer's perspective to think, In order to have a way to fully express the concept of the design diagram.

Earlier, received a "design", there is a "x", I asked the customer what this is, he said is "back to the page", why back to the previous page is "x", this is not a popup is not a modal, and there are many different colors and sizes of "x", respectively, representing the "delete", " Close, slide down, this is a less reasonable design.

Design thinking, will directly affect your writing code structure and Web page structure, because you do not see the focus of the design where, how to write to achieve the results of the designer, you do not have a good way to organize your structure and elements, you can not put together a good web page. This not only greatly reduces your efficiency, but also does not make the same thing. Maybe a Web site, there are several should be the same, the result "very much like" but not the same button, because you use a few classes and different structure to do. You didn't think about design right from the start.

What you can do

1. Nothing to practice, FB stroll a few minutes good, do not need to linger too long.

2. Do a website, play for yourself, play for your friends, ask their opinion? Ask a few more.

3. Look at the design and think about what you will do.

This article is from: Kimix's Blog

http://www.bkjia.com/PHPjc/889925.html www.bkjia.com true http://www.bkjia.com/PHPjc/889925.html techarticle front-end engineers should have three kinds of thinking editor's note: This article through logical thinking, business thinking, design thinking three dimensions to match whether you are a qualified front-end engineer. Because the former ...

