3 ms·
Great article. Move Fast and Break Things always meant “and don’t be afraid that you might accidentally break things, because you eventually will and you shoul
by gorgoiler 7y ago
Great article.
Move Fast and Break Things always meant “and don’t be afraid that you might accidentally break things, because you eventually will and you should just fix them if you do”.
The saying isn’t itself a fallacy but doing the moving fast part without adequate resources to do the fixing part is indeed reckless.
Don’t push on a Friday night. Don’t push without metrics on error rates. Talk to your team. Append instead of overwrite. ..etc.
- danesparza 7y agoAgreed. I always saw this as an extension of "fail fast" -- or an encouragement to experiment (even when those experiments aren't as successful as you'd like). Sometimes, teams get stuck in 'analysis paralysis' -- and this was meant to be a type of antidote. To the folks that say this is a type of anti-pattern, I say: Either you haven't seen this implemented correctly (it helps if you have kids that you want to encourage to explore) or "There is more than one right way to be creative".
- mtberatwork 7y agoAdding: Hire and retain enough experienced staff. Too often these things boil down to one or two engineers shouldering the entire burden of keeping these systems online.
- lonelappde 7y agoYour last paragraph is good advice in many cases but it's saying to not move fast and break things. Twitter rose to prominence on an infamous fail whale. Reddit also was constantly broken. Facebook broke privacy and democracy ;-)