3 ms·
The "new way of doing things" is risky and might not turn out so good after all. If you treat the new way as an experiment, and only gradually convert the rest
by danuker 5y ago
The "new way of doing things" is risky and might not turn out so good after all.
If you treat the new way as an experiment, and only gradually convert the rest of the code, you're in for a smoother ride.
- Spivak 5y agoPlease no, this is how you end up with 20 different experiments and zero consistency in everything. Gradual migrations are fine because it makes project managers happy but it requires a commitment to actually follow through with it. If there's a chance that you won't actually have dev time to finish the migration then just don't do it. It can't be that important then. It's totally fine to try out an experiment in a branch and deploy to QA but don't deploy it to prod until you're sure.
- CTmystery 5y ago> Please no, this is how you end up with 20 different experiments and zero consistency in everything. This comes from a lack of discipline in the org, not from the parent's (IMO) correct guidance that an org should undertake architectural changes with pilots in isolated parts of the code base.