Why are development features getting slower?
One day a technology, he told the boss: the system is too bloated. It's messy, it's hard for me to work, at least it's hard to follow my experience and assumptions. If you want me to do this, the solution is to refactor the system once (refactor the code, or develop a new system to replace the original system).
We make the project much more maintainable. To the company, to take over the technology, are beneficial and harmless.
The results do not allow the next link. Just as the official took office and the term was full. This hot potato is thrown to the next one to solve. In my term of office, it is not possible to maintain stability.
One-sided pursuit of GDP indicators, as if one-sided pursuit of functional completion, regardless of the quality of the completion of the function. The layman is unable to evaluate the quality of the finished function, they can only say: This function has reached my expectations. is good quality.
This is like the GDP reaching the expected target. is good quality. But something important is overlooked.
I find it very much like a system: just make sure I'm in the company this time, the system is stable, you can continue to add functionality to complete the above tasks. As to when the time bomb broke out, as long as not in my tenure broke out.
So I was in office, obviously know here is a pit, are lazy to do code optimization, do refactoring. Why waste your time doing this kind of thing.
Why recruiting experienced technical inputs and outputs is worthwhile. Avoid a lot of pits, leaving behind the technical debt.
I think that at least recruiting experienced technology as a leader leads the people below to have a positive energy.
As the saying goes, crooked Stick throws, the following people are looking at the leadership is what level. Leadership is a kind of technical thinking, the following people will be able to work very well.
Why the new technology is difficult to take over to maintain a system