5 ms·
Great write up. Rushing to institute a new org-wide process as a solution to every problem makes productivity eventually grind to a halt. And at that point it c
by lxe 6y ago
Great write up. Rushing to institute a new org-wide process as a solution to every problem makes productivity eventually grind to a halt. And at that point it can become a vicious cycle of continuous process changes in an attempt to increase quality and productivity.
- user5994461 6y agoThere is a point where preventing people to write code is improving (future) productivity and maintenance. I recall working in a large bank that enforced linting and testing on the whole codebase (monorepo with extensive CI). It's annoying at times but if it were not mandatory nobody would never write any test. Stopping developers/interns/newcomers from adding thousands of lines of random untested code the very first minute they come in (code that would have to be maintained for the next decade by the next people) is a productivity gain for the company. Besides, a good amount of (pet) projects have little or negative value, it's better if they don't exist in the first place.