KuB network front-end_html/css_WEB-ITnose

I once worked for a company. In addition to doing pages and special effects, I also needed to know PHP and some frameworks. I recently went to a company and was asked to do JSP. I didn’t say anything about these before the interview. I passed the interview and didn’t say how much background language I needed to master. In the end, I got it. My own backend looks down on us. One of our buddies left his job. They are all very good at recruiting front-end people. Why do we need the back-end? Could you please tell me, veteran, what do you need to do with the front-end? You can work in the background! Or is it really that those who don’t know how to create background pages in a bunch of JSP codes are just parallel imports?

Reply to the discussion (solution)

The following is just a personal opinion, please share it for reference only and may not be accurate.
First of all, I didn’t mention it during the interview. This is a lesson. Generally, during interviews, I always ask about the specific tasks of the position being recruited. Front-end is a general term, and each company has different task requirements based on the characteristics of its own business. Generally, a responsible interviewer will tell you the scope of work or the specific division of labor, because there is a cost issue here. If the expectations of both parties are different after recruitment, then resignation will inevitably occur. Resignation is a direct loss. From resume screening to recruitment interviews, the cost of this process is in vain. In general interviews, there are many steps, so the baker will not take the initiative to introduce you, but must take the initiative to ask.
Then I looked down upon them, they were all out to make a living, they were all doing things for the company, and they were all trying to get things done. If you want others to think highly of you, you have to argue with yourself.
Then the front-end tasks are divided.
In the past few years, the front-end was mainly to solve the display compatibility problem of the page, or the accumulation of some special effects. It has been slowly changing in recent years, because the needs of social industries are changing, so the job requirements are also changing. I'm only telling you what I know. Recently, the front-end is slowly doing some things in the page views layer, that is, the back-end provides a data interface, and the front-end implements data display, page interaction, visual compatibility, etc. based on the interface.
As far as my personal experience is concerned, the company I am currently interviewing has the same experience as you. During the interview, it was said that the backend is java, but now the front end is .net razor template, so I have to learn everything from scratch. How do you actually say it? I feel like the techniques are the same, and there’s no harm in learning more when you’re young. I regard this job as a rare learning opportunity, and strive to prepare technical reserves or accumulate professional experience for my next job change. If I have any questions, I humbly ask the newly graduated .net graduate students for advice. The handsome guy is also quite enthusiastic and helpful. Their overall feedback to me was equally passionate, and I never felt that they looked down on me. Through this sharing, I want to illustrate that sometimes the control of communication mainly lies with you.

Now I am also working on a website, but I have to learn HTML5, JSP, jquery in many directions...

The goal of jsp It’s just for the front end to work.

jsp is all about front and back

I believe there will be someone dedicated to the overall framework

Come on! ! ! I will start recruiting soon! ! ! Also do the front-end! ! ! [The road is long and long, I will search up and down] I will encourage you~

It’s hard work, it’s all

I’m looking at bootstrap and jquery for the backend