In recent years, with the rise of single-page web applications, all kinds of frameworks have kept emerging.
The front end has begun to enter a stage of engineering and componentization.
Single-page web technology has expanded the boundaries of the front end, which can now also route and render pages without depending on the back end.
The focus of backend work has shifted to a pure data API service.
With the spread of all kinds of BaaS cloud services, the value of the backend providing API data interfaces is declining.
A website without traffic has no value. Development that nobody needs likewise has no value.
In a front-end/back-end separation development model, how do we once again demonstrate the value of the backend? The following capabilities can be improved:
1. Requirements Analysis
- Discuss and analyze requirements together with the PM, act as a technical consultant, and flag technical difficulties.
- Integrate the existing internal technical resources and offer input.
2. Problem-Solving
- For a given requirement, propose a solution and write a solution document.
- Resolve the problems encountered during development. For example, authentication for frontend interfaces, and so on.
3. Interface
- Provide frontend interface documentation.
- Maintainability.
- Extensibility.
- Performance testing.
4. Management
- Project scheduling and planning.
- Daily stand-up meetings and meeting notes.
- Project follow-up, feedback, and risk exposure.
