My answer is - you need to learn and understand, but you don’t need to be proficient. To what level is it specific? You just need to be able to understand what the front-end engineer writes. After all, HTML+CSS+JavaScript is the final output content. If you If you don’t understand what the output is, how can you do a good job in back-end development? Broadly defined back-end development refers to accepting request URLs and finally dynamically outputting resources. The Web front-end in a narrow sense refers to pre-assembled dynamic pages and delivering them to back-end engineers for output. So understanding is necessary, which is why general back-end training will first learn HTML+CSS+JavaScript. But I prefer that front-end and back-end engineers should learn from each other in addition to their essential work. As mentioned above, there is no harm in learning more. Be prepared and you will be safe. When Node.js first came out, the first people to come into contact with it were front-end engineers who knew the back-end. PS: Let me correct a small mistake for you. Web front-end technology is only HTML+CSS+JavaScript. BootStrap is just a set of front-end component libraries. As far as I am concerned, its biggest role is to prevent a back-end engineer from having to worry about the front-end. You can create a nice page. But the real front-end disdains to use it, because if you want to use it to write your own style, you have to overthrow the basic styles and start over, which will cause serious dependency problems.
Depending on how you position yourself, it can be divided into the following categories:
System backend: Responsible for various system middleware and pure backend services, basically not dealing with frontends and clients. There is basically no need to learn this kind of thing, as long as you know what is going on.
Application back-end: Responsible for application services, closely related to business, and dealing directly with front-end and clients. You need to understand this, and maybe even write some management pages yourself.
Full-stack partial back-end: Often the back-end wants to transform into a full-stack, but the focus of companies and projects will still focus on the back-end. This must be learned. Even if you are not proficient in it, you are at least familiar with it.
Full-stack partial front-end: It is often the front-end that wants to transform into a full-stack. There is no need to say this, you must be proficient in front-end knowledge
If the subject of the question focuses on back-end development in the future, my personal suggestion is to thoroughly consolidate the back-end technology. There is another point where I differ from the above answers: since I have thought about my career plan, I should also try my best to let the company and projects rely on me instead of relying on the company and projects myself. I decided to focus on the back-end, so I worked more on the back-end things in the company. Sometimes I really bit off more than I can chew, and ended up with nothing.
This question depends on your environment. If your company has a very clear front-end engineer, and you are not very interested in the front-end personally, then you only need to get familiar; If your company is a lean team, people If you do less and do more and there are no clear front-end and back-end positions, then you may develop in the direction of full-stack engineer.
But, it never hurts to learn more. The characteristics of different languages sometimes give you special inspiration. For example, when I write java asynchronous programming, I will refer to ajax in js (maybe not a very appropriate metaphor ), I will refer to the ideas of java when writing js.
As for the technologies you listed, I am only at the understanding stage of css and jq (because I have learned angular and vue before, so I have not learned jq), and the level of js is average (stuck at the business code stage). As for Bootstrap is already easy to use and feels familiar.
PS: I feel like this kind of question should be better asked on Zhihu.
I think you need to understand this. The degree of understanding is optional. After all, full-site engineers are also excellent, but people have specializations. It is best to stick to their own job, supplemented by learning and understanding. The key point is not to be fooled by the front-end!!! !
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
My answer is - you need to learn and understand, but you don’t need to be proficient. To what level is it specific? You just need to be able to understand what the front-end engineer writes. After all, HTML+CSS+JavaScript is the final output content. If you If you don’t understand what the output is, how can you do a good job in back-end development? Broadly defined back-end development refers to accepting request URLs and finally dynamically outputting resources. The Web front-end in a narrow sense refers to pre-assembled dynamic pages and delivering them to back-end engineers for output. So understanding is necessary, which is why general back-end training will first learn HTML+CSS+JavaScript.
But I prefer that front-end and back-end engineers should learn from each other in addition to their essential work. As mentioned above, there is no harm in learning more. Be prepared and you will be safe. When Node.js first came out, the first people to come into contact with it were front-end engineers who knew the back-end.
PS: Let me correct a small mistake for you. Web front-end technology is only HTML+CSS+JavaScript. BootStrap is just a set of front-end component libraries. As far as I am concerned, its biggest role is to prevent a back-end engineer from having to worry about the front-end. You can create a nice page. But the real front-end disdains to use it, because if you want to use it to write your own style, you have to overthrow the basic styles and start over, which will cause serious dependency problems.
Depending on how you position yourself, it can be divided into the following categories:
System backend: Responsible for various system middleware and pure backend services, basically not dealing with frontends and clients. There is basically no need to learn this kind of thing, as long as you know what is going on.
Application back-end: Responsible for application services, closely related to business, and dealing directly with front-end and clients. You need to understand this, and maybe even write some management pages yourself.
Full-stack partial back-end: Often the back-end wants to transform into a full-stack, but the focus of companies and projects will still focus on the back-end. This must be learned. Even if you are not proficient in it, you are at least familiar with it.
Full-stack partial front-end: It is often the front-end that wants to transform into a full-stack. There is no need to say this, you must be proficient in front-end knowledge
If the subject of the question focuses on back-end development in the future, my personal suggestion is to thoroughly consolidate the back-end technology. There is another point where I differ from the above answers: since I have thought about my career plan, I should also try my best to let the company and projects rely on me instead of relying on the company and projects myself. I decided to focus on the back-end, so I worked more on the back-end things in the company. Sometimes I really bit off more than I can chew, and ended up with nothing.
No need....
This depends on the company you join. I personally recommend learning more and developing in the full-stack direction
You will definitely use these when doing javaweb.
Unless you are professional in interfaces or system integration
This question depends on your environment.
If your company has a very clear front-end engineer, and you are not very interested in the front-end personally, then you only need to get familiar;
If your company is a lean team, people If you do less and do more and there are no clear front-end and back-end positions, then you may develop in the direction of full-stack engineer.
But, it never hurts to learn more. The characteristics of different languages sometimes give you special inspiration. For example, when I write java asynchronous programming, I will refer to ajax in js (maybe not a very appropriate metaphor ), I will refer to the ideas of java when writing js.
As for the technologies you listed, I am only at the understanding stage of css and jq (because I have learned angular and vue before, so I have not learned jq), and the level of js is average (stuck at the business code stage). As for Bootstrap is already easy to use and feels familiar.
PS: I feel like this kind of question should be better asked on Zhihu.
Clearly said no. What matters is whether you use the time you save to eat, drink, have fun, or improve yourself. This is what determines your future.
I think you need to understand this. The degree of understanding is optional. After all, full-site engineers are also excellent, but people have specializations. It is best to stick to their own job, supplemented by learning and understanding. The key point is not to be fooled by the front-end!!! !