3 ms·
If your goal is to get rid of A by any means necessary, make the business decision to turn off A at some point. Not having the backbone to make that decision a
by sokoloff 7y ago
If your goal is to get rid of A by any means necessary, make the business decision to turn off A at some point.
Not having the backbone to make that decision and allowing the call to forced at some arbitrary time by a bug and concluding the bug was a good thing (or at least had a silver lining) because it allowed the org to move away from A suggests a possible leadership decisiveness problem to me.
- user5994461 7y agoThere is no organization of more than 500 employees that can take decisions like that. Developers of one service simply don't have the power to force other developer in another part of the organization to do anything. That's assuming they're even aware of the existence of that service and who is supposed to own it.
- sokoloff 7y agoSomeone has the ability to make that decision. CTO or CEO in the worst case. Having the decision "made for you" and being happy/relieved about it doesn't seem like the healthiest or firmest hand on the tiller way to run a company.
- 8note 7y agocounterexample: the team I'm working on has successfully turned off ~10 systems with/without replacements, and got all of our clients within a much larger than 500 person org to migrate fully.
- user5994461 7y agoI am not saying it's impossible. I'm doing that with hundreds of systems covering 5000+ developers/clients. Fact is, it's a nightmware to handle. It just takes one client who can't or won't upgrade and it's blocked forever.