I totally agree that going slower is faster.<p>I disagree that the problem is cowboy coding. I&#x27;d identify the rope as carefully understanding the actual goals of the software and the way it functions in the world. Good engineering teams going &quot;ropeless&quot; rarely fuck up in a technical sense. I&#x27;ve been writing software long enough that my engineering judgement is usually pretty solid. Where they fuck up is building tons of extraneous functionality with the extra capacity, losing touch with what their software <i>actually does</i> in the world.