|
|
|
|
|
by daveguy
299 days ago
|
|
To be fair. "Move Fast and Break Shit" was a garbage motto to begin with. Maybe better to be at least slow enough to realize the consequences of a broken app. If you're moving too fast and breaking too much shit, you won't know you have a suicide-assitance app until it's too late. So, it was a garbage motto to begin with and it's about time it's been taken down a notch, in my opinion. How about move fast and test/verify/validate shit instead? That way the entrepreneurs don't have to go full sociopath. |
|
> How about move fast and test/verify/validate shit instead?
Because that inherently isn’t moving fast.
I don’t completely agree with the “Move Fast And Break Shit” mantra myself, but I think it comes out of genuine frustrations from the enterprise world.
I worked at a BigTechCo [1] in the past, and it felt like I would spend twenty minutes doing a ticket, and it would take two days for everyone to “verify” my PR. Even doing a quick fix for a null pointer exception can take three or four days to get deployed as a result of this. The stuff I was working on was not high stakes. I wasn’t dealing with money or medicine or pacemakers or weather analysis or anything like that.
The Move Fast and Break Shit stuff comes as a bit of an overcorrection on this, but I think fundamentally the idea is that a lot of this stuff really isn’t that important, and it’s better to just deploy something that “probably works” and fix problems as they happen.
[1] It’s not too hard to find based on my post history but I politely ask you do not post specifics here.