Comment by spencerwgreene

Nothing in the post is wrong, but there's an anti-pattern where teams resist change, the software ossifies, and people cite these mantras like "slow is smooth and smooth is fast", when in reality the users just want new features shipped on the order of weeks/months, not quarters/years. Users eventually lose patience, leave or fork the code or solve their problem differently, and route around the team that doesn't get stuff done.