Page Refactoring Professional: page Refactoring Engineer's practice strategy

Web page Production WEBJX article introduction: Web Refactoring Division's advanced strategy.

All along, I would like to hope that through their own sharing, can let more peers have harvested, especially a certain foundation, has been to the bottleneck of the students to find a breakthrough. Of course, my own experience is too little, this hope is purely yy, but there are goals at least the direction of doing things, I will do it on my own.

Say back to "page refactoring engineer Practice slightly", the reason will take this as the title, mainly the team of new students brought me a lot of different ideas, began to pay attention to the "specialization" topic.

First look at the overall content:

Divided into three major parts:

• To "downstream"
• To "upstream"
• For the team, their

First, take a look at the "upstream" and "downstream" of the workflow. As a page refactoring engineer, did our own work before you were a professional page refactoring worker? And reread "Are you a professional page refactoring worker?" There have been more discussions, but what can the page refactoring engineer do in the whole process?

To "downstream"

Often hear so-and-so complaining about the "upstream" how, indeed many seem to "extra" workload, is due to "upstream" generated, will produce complaints is normal, human nature. But calm down, don't forget we also have "downstream." As "upstream", your output directly affects the "downstream" efficiency. Therefore, we need more in the output time for the "downstream" of the work to provide convenience.

Remember in a training class the teacher talked about an example, of course the theme was different from what we're talking about today, but I think it's quite enlightening: "In an E-commerce site, in order for the user to get a better experience, the interaction designer designs a region that tracks shipments after the user orders, It is a good experience to display each time node of the manifest on top, including the current state and so on. As a result, the developer responsible for development said, the cost of this function is too high, and the logistics company is a third party, we can not get the relevant data ... Finally, the result of the discussion is to change into a link to the third party logistics company's order query system, the user to check, the page only provides a portal. "Also like the effect of the simulation Pull-down menu and the use of the System Pull-down menu is much worse, may be a small change upstream, will bring a lot of changes in the downstream-the process of the" butterfly effect.

From the refactoring of this ring, for the "downstream" to provide the convenience is mainly the content of the code, like in the code to add a reasonable, adequate annotation, to guide the downstream faster to find the necessary parts, code, etc., but also can contact, understand the work downstream, like learning JavaScript, such as the implementation of methods, To improve the output of our pages can be more easily implemented.

To "upstream"

The term "technical restrictions", for products and design of the students, should be familiar with, but also a very annoying word, because always because of "technical limitations", need to be satisfied with the original works to modify, for the downstream to make a compromise. There has even been a time when the team has a "technology-restricted product development" of a storm, the details do not need to be carried out can be imagined. Look at it from another angle? I like to change a point of view, often listen to the program of the students said "only unexpected, not achieve." "Let me think of Archimedes's" Give me a fulcrum, I will pry up the whole Earth. "So, can you really find this fulcrum in real life?" If the product was set up at the beginning of a very conceptual, idealized, ignoring the reality of the environment, conditions, then the product will not be able to achieve or extend the term.

In the request "upstream" students learn to understand the "downstream" work, as a "downstream", we should also be "upstream" to provide certain training, so that "upstream" more understanding of our work and the help to complete the work. Can reduce the "upstream" output is not real value of content, do not work hard, but also to provide more complete content. It can even provide an "upstream" way to improve efficiency from our point of view.

, from the perspective of refactoring, for the "upstream" to provide help, "Web page production base", "Web page production process", "Photoshop action Production" and so on content training, may be strange why PS action will be in them, most of the designers are not too cold, although we are not in the design of the line, But for the programmatic PS action, the master is still very fast. Well, it's also a good way to help designers accomplish a certain type of action, and help improve productivity.

Above is the process in the "upstream, downstream" angle of the content, can be summed up as a sentence: "To get the trust downstream, trust you upriver!" ". In addition to the above content, there are some small tips that can quickly improve efficiency: like "Long Code, save text as TXT file", "confirm the question to the positive response", "provide the other text needed, to copy" and so on. In these scenarios, the sender is "upstream", and the receiver is "downstream." There are a lot of things to do and we need to think more.

For the team, for their own

The technical work of the students are very clear or will be clear: the technology itself is not fun, the real fun to use technology to solve a problem or achieve a certain function, effect. Another designer can understand: "Photoshop itself is not fun, the real fun is to use Photoshop to achieve the desired effect." "I have learned from the truth that the pleasures of work can be created by themselves." What's the fun?

Provide your team with more efficient solutions, accumulate, think, and explore better specifications, processes, tools, methods, etc. in your work. Share your solution, it is best to form a certain positive competition within the team, to keep your team alive.

Perhaps a lot of students "not confident", that even if the team have such people, it will not be their own. What does it matter? It's just a way to make your work fun. Each person's point of interest is different, as long as the positive, will find the fun.