Is the first development force of science and technology | | to fish in troubled waters
Countries have said that science and technology is the first development force, can not touch the technology is not good technology, so the following I write things are used to help everyone to better fish in troubled waters, of course, touch the fish is also to rely on technology.
Front piece
During the development of our company, the most interesting thing is that PRD takes two months to write prototype, one month to draw UI, half a month to develop and one week to develop. Every time at this time, I always hate why I am not a big man, but I have no way to become a big man, so I use a roundabout strategy to shorten my development work time. I started out as a vegetable chicken, just taking everything apart into common components
(Lazy screenshots of the online environment, in order not to expose please allow me to type a code)
All kinds of reference infinite dolls, at the beginning of the time is really very happy, reference to modify THE API task completed.
And then one day our dear QA sister came to me, and we had detected a problem in one environment, and we were able to reverse verify that it could be replicated online, and that’s a problem you need to fix. At this time, MY face was ❓❓❓, and THEN I started the investigation. I found that the preliminary design did not take into account that trigger would be triggered in some cases, which would cause change to be triggered when I opened it again after reset. Then AFTER the investigation, I thought it was not a small problem, so I just said to change it and mentioned the testing environment after the verification. Did you think this was the end of it? Too Young too Simple we have more than a dozen online branches, each corresponding to change, at this time I lost a lot of hair, here thanks to Beyond Compare let me save a lot of effort, but, in order to avoid the occurrence of my only little hair, I bitterly abandoned this method.
Formal paper
First, I maintain my components as NPM packages. The advantage of this is that every time I have a problem, I only have to change one place and then update the version of the project.
Said the design thinking, first of all to better fishing, I inherited a out-of-the-box thinking, is the foundation of all functions are encapsulated in entirely, but at the same time take into account that there are some special cases, to make it open, and use the default priority as guaranteed, or it will cause a lot of use!
Then I’ll review the NPM release process
The first step: simply create a project with Simple, and then write the components and methods
Step 2: Create an index.js file to export the file
Step 3: Modify the package.json file
Step 4: Modify webPack.com FIG
Step 5: Make a package and reference it locally to see if there is any problem. If there is, modify it for a specific problem. If there is not, go to the next step
Step 6: Upload to NPM, water finished…
At the end
The Nuggets didn’t use it much, but they’ll move to the nuggets later. Secondly, I originally intended to write a pure article about fish. At the beginning, the paragraph was just to mock our company, but considering that it is a technology after all. Although this article is very basic, it can be regarded as the foundation for the later, because the project I am in charge of involves the transformation from Shit mountain to micro front end. There is also the cloud project, so I will write step by step from the transformation I took over the play, the illustration may be filled with a lot of Mosaic, because sometimes I do not have a demo to use. In the end, this is a nutrient-poor piece of hydrology, just to mention the basic package. In the next article I will water a few pages of small functions in the micro front release use, should have a little bit of use it… Don’t spray, big guy