News for hackers. Stuff that matters.
Re:The Fallacy of Move Fast and Break Things by mrlala on Monday March 23, 2020 @12:46PM (#22665809)
>"Move fast and break things"--said no carpenter, ever.

Worst analogy ever. If we had GIT for woodworking you would see productivity skyrocket. But you can't restore wood like that. You can't restore pipes, wires, structures like that.

Code.. you can. So get out of here with your analogy. I can move at a very fast paced coding new ideas at times, or implementing random stuff knowing I will probably break stuff. But you know what? I can fix that afterwards. It doesn't matter that I broke something to get something else to work.

Re:The Fallacy of Move Fast and Break Things by DoofusOfDeath on Monday March 23, 2020 @01:54PM (#22666702)
I think the carpenter analogy is actually very good: it gives us a starting point for thinking about where MFABT is / isn't a good idea.
Re:The Fallacy of Move Fast and Break Things by jmhnilbog on Tuesday March 24, 2020 @02:03PM (#22676996)
Reverting won't erase your users' poor experience with your product.
Re:The Fallacy of Move Fast and Break Things by Finnucane on Monday March 23, 2020 @02:42PM (#22667220)
And do you make your users suffer your broken stuff?
Re:The Fallacy of Move Fast and Break Things by mrkeen on Monday March 23, 2020 @02:45PM (#22667247)
Can you fix data?