4 ms·
My sense of the problem is that it's not so much a tech stack issue and more of an operational, "keeping the train on the tracks" challenge.
by mud_dauber 10y ago
My sense of the problem is that it's not so much a tech stack issue and more of an operational, "keeping the train on the tracks" challenge.
- HelloNurse 10y agoPersonal problems, communication failures, and organizational issues are often reflected in code and technical choices. For example: - Something gets rewritten because requirements were lost or misunderstood. - The same error is repeated after being corrected. - A component is revised or eliminated, after having been developed too early based on guesswork and speculation. - Developer A commonly reverts developer B's code changes without explaining the reasons (or with insults). - There has been a messy, error-ridden merge between the clearly independent developments of two sub-teams. - In source code control, commits are allowed to lack a good description; only a few true believers "waste time" with messages nobody reads. - Unit tests for something that is approaching release were last modified, and left about 15% complete, six months ago. - After employee X left the company (or when the project devolved into crunch mode, or some other excuse) automation of builds, tests, releases etc. started to rot.