Many leaders of the development department will think of the opportunity to start afresh when they resume a failed project, and use the most popular and popular technology stacks (spring boot, springcloud, redis, nosql, docker, vue), and they can definitely do the project. Quick and good.
This kind of blind follow-up to the just-popular yet immature technology and the careless selection of technology are very common. The technology stack that is outdated in their eyes today is actually just a trend of another group of people a few years ago.
I do n’t oppose technological chasing, but the problem here is: they only know how cool the new technology is, they do n’t know how many pits the new technology has n’t encountered. Because of inexperience, often a small problem will cost a lot It takes a long time to solve it; I am not sure or thinking deeply about how to avoid repeating the same mistakes and using the new technology architecture to make another bad project, but I am blindly optimistic that the new technology can bring success.
No one can stop the impetuous atmosphere of this type of resume-driven technology selection. After all, it takes the company's resources. It seems that it is very pursued with new things. Failure will not affect the beautification of the resume. Only a project resume and a resume will be added to the resume. Several kinds of proficient skills will not mention that another rotten project is done, and fame and fortune are both successful and profitable.
So the reason for doing bad projects is not because the technology is too backward, but the collective self-healing of the so-called technical masters;
