'Programmer 'and 'website'

When I took a Software Engineering Course, the most BS in the instructor's mouth wasProgramPersonnel-programmers are the least promising, no matter how manyCodeDealing with things is always just a 'blue-cycle '. At that time, when I took this course, I really thought that I had learned software engineering and could surpass programmers to become an engineer --

I dare to ask, which software engineer did not crawl from the program stack?

Since I have made many front-end projects, I have been mixing them in many forums, Team blogs, and Master blogs for a long time, I finally heard that there is a profession called 'page Z' in the industry. I guess that the first person who uses 'page' to call a profession should be a programmer.

However, the relationship between 'page' and programmers and between programmers and software engineers is completely different. Programmers write a lot of programs. Maybe they haven't even found themselves one day, and they are already engineers, but there are more pages created by the 'page, it cannot be called a programmer in any way.

'Page' also writes CSS code, HTML code, and even JS Code! That's right, but are programmers writing code?

We can divide the Web Front-end into three parts without responsibility: structure, performance, and behavior. The occupations that prefer 'behavior developing' need to be separated and called 'front-end development engineer ', those who prefer to study the structure and performance are called 'page engineer', 'page architect ', or 'page reconstruction engineer. I am not here for literacy, but for learning-Why are backend programmers so BS front-end developers? Yes, some people can create an e-book 'one week to learn to cascade the style table' to read and write on the Internet. Some people can use 'ten days to make you a JS master'-however, is it so easy to learn CSS, is it so easy to become a JS master?

A "CSS authoritative guide" has made me study it for countless times. I learned that I don't know several selectors, but that I know the meaning of several attributes and Their attribute values, even if I know 'css. 'Stacked style table'-'style' is very important, and 'stacked 'is more important. First, regardless of browser compatibility, CSS particularity (priority) is not understood, CSS cascade is not understood, the 'expression' of 'design 'can only be a pile of unmaintainable garbage! W3C's Implementation of Web standards is nothing more than an aim, not to make websites easier to develop (in fact, it is more difficult to develop strictly according to the standards), but to make websites easier to maintain and expand. -- That's right. backend programmers can easily create 'appearance-compliant pages', but backend programmers may not be able to create a 'maintenance-friendly 'page!

At this point, it seems that there are thousands of questions. When the peak turns around, do 'website' really deal with 'programmer? No.

Taking into account the merits of previous-level figures developed by front-end developers, the page creation has been refined to study the structure and semantics of HTML. In fact, the most overlooked labels seem to be 'physical style-based tags' and 'content-based style tags'. However, is HTML too focused on 'semanti? We often use one word: Structure semantics. I dare to ask: "Have you made the structure before the semantics ?"

The browser parses HTML into a DOM tree, which is a classic data structure, javascript can easily 'traverse '-'tree', 'Data struct', and 'traversal'. Isn't it what programmers often talk about? Each design draft is parsed by different page architects and will certainly get different Dom trees-I have always had an intuition, and one of them must be the best design, for example, there will always be a JS search tree.

I have participated in the interview for the job 'website'. I always like to emphasize that I know 'JS. Small companies will think that you know JavaScript, PHP, and database ...... The big company is: "If you know JS, we suggest you invest in our company's Web Front-end development position ." -- Difference!

Are the 'website' and 'programmer 'completely separated? Not all!

Can 'page' and 'programmer 'be confused? Even worse!

Therefore, this article obfuscated the 'website' with the 'programmer '. It was originally an error-not to mention it ......