@david_whitney I think if places don't have robust deploy pipelines then "revert your changes" can be a daunting task. There's also the fear of corrupting some data which is non trivial to revert
A brilliant honest article about changing your mind on HS2.
Some change their minds when they discover the benefits instead of just hearing the costs.
Some change their minds when they realise how much is already built. https://t.co/WC9gRymd1V
@miss_jwo For me: dried seaweed because I can dump it in anything liquid and pickles because you can serve almost any meal with a side of pickled veg. Both last well so reduced the need for planning
@MattJamesBoyle It wouldn't be a deal breaker but 100% remote is a negative. I like meeting in real life at least once a week. 100% office is a deal breaker though
@henrikwarne Yeah I definitely agree it's less useful for products. And it's definitely not a hard line (as you mention). For example if functional programming becomes big in a language is adding a functional interface to a library maintenance? I think I mostly use the opposite, unmaintained.
@rickasaurus@vboykis@t0yv0 This only works short term. After the rest they get stronger and more resistent. Before you know it you're having to get up early to take them to triathlons
@henrikwarne In the first two I would say the software is being maintained. In the last I wouldn't. In the first I would say it's undergoing feature development as well as being maintained