3 ms·
At big companies this attitude eventually yields a stagnant product. No one is confidant that any impactful change wouldn’t break something and no one knows if
by lumost 5y ago
At big companies this attitude eventually yields a stagnant product. No one is confidant that any impactful change wouldn’t break something and no one knows if that something even matters to customers. Even worse there may be teams that will make 0 changes as they’ve been marked as KTLO.
Having tooling to acknowledge that in fact no one will be affected by a change is a huge productivity boost.
- dec0dedab0de 5y agoHaving tooling to acknowledge that in fact no one will be affected by a change is a huge productivity boost. Yes I do agree with that part
- nradov 5y agoYears ago I was blown away when I saw a presentation by a Google Java library developer. He was able to make changes to his library, then automatically build every Java application throughout the enterprise which used that library to check for automated test failures. This allowed the library team to move fast with confidence.
- wikibob 5y agoAnd you can too! http://Bazel.build http://Bazel.build
- underwater 5y agoKTLO = Keeping the lights on, for anyone else who hasn't heard the acronym before.
- jnxx 5y ago> At big companies this attitude eventually yields a stagnant product. Such as Linux?