Is the front-end development tired or the back-end development tired?

Both front-end development and back-end development are very tired, almost.

1, front-end development:

The "front end" of the website is the part that directly interacts with users, including all visual content that comes into contact when browsing the webpage-from fonts to colors, as well as drop-down menus and sidebars. These visual contents are presented by parsing, processing and rendering related HTML, CSS and Java files through browsers. Front-end development is to create code behind the user-oriented part of the website mentioned above, and build an immersive user experience by building a framework. In order to achieve this goal, development needs to be proficient in the following languages, frameworks and tool libraries.

2. Back-end development:

In order to make the server, application and database interact with each other, back-end engineers need to have server-side language, data-related tools, PHP framework and version control tools for application construction, and skillfully use Linux as the development and deployment environment. Back-end developers use these tools to write clean, portable and well-documented code to create or update Web applications. But before writing code, they need to communicate with customers, understand their actual needs and turn them into technical goals, and formulate the most effective and streamlined scheme to achieve these goals.

The biggest difference between the two lies in the way of display, the technology used and the direction of thinking. Moreover, the front-end development is easy to get started, but after deepening, you will find that there are many things to master; Back-end development is difficult from the beginning, and it needs to deal with a lot of business logic codes frequently. Therefore, whether engaged in front-end development or back-end development, no one is better and more promising, and the career development prospects mainly depend on personal ability.

On the issue of program complexity, if the scale of your program is directly proportional to the program complexity, it means that there is something wrong with your program architecture. In other words, with the increase of the project scale, the complexity of the program can not be significantly increased. It is precisely because of the increase of program complexity, not the increase of workload, that the maintenance cost is getting higher and higher, and you will need more and more back-end personnel or front-end personnel for the next work. ?

At this point, it mainly depends on how the architecture of your program is designed. If your back-end is very complex, of course, you need a lot of people, and the front-end is actually the same. The reason why the back end needs a lot of people is mainly complexity, and the reason why the front end needs a lot of people is mainly workload.

This is also the difference between the front end and the back end. Another backend is sometimes used to monitor services, for example, a condition can trigger SMS, email, etc. There is no need for front-end collaboration, which is regarded as a workload of a separate back-end. But for the convenience of management, even these data generally need to be managed by writing a set of front-end.