Identify development pain points
When I used elementUi, I had to go to the official website to copy the demo code every time, which was a hassle, but I kept repeating the same tedious work.
It wasn’t until I realized this was a pain point that it occurred to me that the ele demo could be written as vscode snippets to improve development efficiency. I learned that there are already a lot of vscode snippet plug-ins for common component libraries and tool libraries.
Imagine if I had realized this earlier, I would have been more than just a user, and maybe I would have made these great plug-ins.
Real pain points lead to good demand, and good demand leads to good products.
Note: It is not difficult to solve the pain point, but to find the pain point, the difficulty is to have the habit of thinking constantly looking for and finding the pain point.
Ps: you can search for elementui in vscode’s plug-in library. Similarly, public libraries like lodash have snippet plug-ins. Salute to excellent peers! New one!!!!!!
What else do we need to think about as we develop
When you ask a Bull for advice, they always tell you to think about everything. But this is like chicken soup. What do I need to think about? It doesn’t help me to think about who won the US election when I was developing.
The first half of the article summed up as follows: When developing, always think about whether there are development pain points and how to improve development efficiency. This actually mentions the concrete implementation of the thinking direction. In the actual development, I also summarized many of these thinking directions and considerations:
- Is the current technical solution optimal? Whether there is room for further optimization
- Is my code simple and easy to understand and maintain? Business processing logic, names of various variables, and so on
- Is the work I am doing repetitive? If so, can I build my own wheels to improve development efficiency?
- Do you really understand the requirements you are responsible for and the reasonableness of those requirements
- The rationality of UI UE
- Always look at your product from the user’s point of view
This is just the tip of the iceberg that I understand. These are all directions for growth and learning to think. Truly practice it and you will not be far away from the bull.
If you have other points you need to think about in the development, feel free to share them in the comments or make an issue on Github. I will sort them out and update them constantly.