Highly Agree. Speed of all kinds is incredibly important. Give me all of it. - Fast developers - Fast test suites - Fast feedback loops - Fast experimentat

Highly Agree. Speed of all kinds is incredibly important. Give me all of it. - Fast developers - Fast test suites - Fast feedback loops - Fast experimentation Someone (Napoleon?) is credited with saying "quantity has a quality all its own", in software it is "velocity has a quality all its own". As long as there is some rigor and you aren't shipping complete slop, consistently moving very quickly fixes almost every other deficiency. - It makes engineering mistakes cheaper (just fix them fast) - It make product experimentation easy (we can test this fast and revert if needed) - It makes developers ramp up quickly (shipping code increases confidence and knowledge) - It actually makes rigor more feasible as the most effective rigorous processes are light weight and built-in. Every line of code is a liability, the system that enables it to change rapidly is the asset. Side note: every time I encounter JVM test startup lag I think someday I am going to die and will have spent time doing _this_.