I appreciate the fact that IMB is trying to present a optimistic view of the future. Not all sci-fi needs to be negative or dystopian, and his remains plausible despite its optimism.
I think if you’d rather read about the downfall of the Culture, then you’ve somewhat profoundly missed the point of Ian’s writing.
1. Exercise good judgment about what projects are “away team-able”. Be okay saying “this needs to be done by our team” even when that’s hard. Otherwise you’ll end up with tricky features implemented by people who don’t understand the full context (this sucks very badly)
2. Make sure the amount of process matches the amount of complexity. If the change is very simple or only a few lines, make it trivial to submit code changes that will pass review. (So have really good automated style checks/test suites.) If the change is complex, make sure you’re doing design reviews before implementation, to ensure the away team doesn’t waste time with bad implementation strategies
How does that work when the thing you want to change is a complex micro-service with a public API? Do you want to spin up your own version of that service and own it forever? Even if you’re okay with that, you’ll not have the clients the older version has
Open-source model works for libraries, or small changes in service code (where the maintenance burden is trivial). But it doesn’t work for complex services with high maintenance burdens
This should never happen on Prime Video. Major breach of customer trust.
If it’s happened to you please call customer service and complain. If they can’t fix it or refund you, please get in touch with me and I will try and get it fixed for you
I feel like this is easier if you’re a non-lever-puller. If you think it’s wrong to pull the lever if it causes anyone’s death who wasn’t dying anyway, then most of these are easy.
Except the “you can’t see the track” one I suppose :P
I think if you’d rather read about the downfall of the Culture, then you’ve somewhat profoundly missed the point of Ian’s writing.