2 ms·
There are many failure modes, and by the time you show up... the entrenched incompetence will constrain the options within current project inertia and budgets.
by Joel_Mckay 3y ago
There are many failure modes, and by the time you show up... the entrenched incompetence will constrain the options within current project inertia and budgets.
Usually, it is better to branch a separate "new" team in another space, functionally deprecate the old project one feature at a time, and jettison the previous team including the manager after 6 months of uptime.
Trying to untangle a mess often takes 7 times longer than simply re-building a better version with well defined use-cases. =)
- Arrgh 3y agoCounterpoint: the new project has to survive long enough to ship 1.0. :/
- Joel_Mckay 3y agoSometimes a company is not worth saving, and it is better to reject the project before the stench stains your reputation. https://www.youtube.com/watch?v=6D9vAItORgE https://www.youtube.com/watch?v=6D9vAItORgE =)
- PH95VuimJjqBqy 3y ago> by the time you show up... the entrenched incompetence will constrain the options within current project inertia and budgets. this is so true, but sometimes the incompetence is so bad it's not feasible to build a competent team (very very difficult at least). I'm actually in the middle of this now and I have to tell you, I've been doing this for 25+ years and I'm absolutely flabbergasted that people with this level of incompetence are gainfully employed in this industry. It's so bad we have contractor teams running circles around them and by circles I mean 2-3x their velocity with code designs that are as good or better.
- Joel_Mckay 3y ago"I've been doing this for 25+" Indeed, people from the early days actually know how a computer is internally structured. I seriously consider becoming a Plumber everyday. Had to develop esoteric personal projects to find the fun. =)