break fast 🥣 move things 🛒
break fast 🥣 move things 🛒
particularly move your cv to the blank email
"we've had one break fast, yes. What about second break fast?"
65Do you work in devops?
16
21Dev oops
14
I believe we call that a "fast follow".
2
Like all sayings, there is context for moving fast and breaking things.
The saying means that when creating something new for profit, don't worry too much about trying to figure out all the details beforehand and figure it out as you go. This will inevitably cause things to break, but being able to quickly fix that when it happens is the same skills needed to create new features as you go.
The saying does not work with large and complex established systems where breaking things wreak havoc.
55It also feels like they chase the “break things” part as if not breaking stuff is a bad thing, and like we should be proud of them for releasing broken and poorly tested updates.
Move fast, break things, fix the broken things, push update/product whatever. They keep forgetting the third step.
21Like the startups that 'disrupt' the established system by ignoring laws and breaking the parts that worked and selling it like an improvement.
'Ride sharing' (unregulated cabs) was only cheaper because of investor funding allowing them to undercut on pricing, abusing the concept of contract workers, and the companies ignoring laws. That isn't 'disruptive' by being innovative, that is cheating the system.
15I think there is another aspect that is important: limit the blast radius. Shit inevitably happens when you create something new and complex, and when it does, you’d rather minimise the impact where possible.
7
And more likely to overall fail. https://www.theregister.com/2024/06/05/agile_failure_rates/
3
come to think of it, at this company devs aren't needed, just QAs and a toxic manager would suffice
44oh, that's how you end up with
APERTURE SCIENCE33for those who wanna drown in nostalgia a bit
7
but what about the auto tests
17Management said that writing tests takes too much time and eats into the time that could be used to write features for the app, so they decided that we're not writing tests. They were always green anyhow
40Tests are for nerds.
4Programming is also for nerds.
Therefore, tests are for programmers.
◼
4
Always remember, the silicon valley ethos of "break things" wasn't about their applications, it was about breaking industry, society, laws and your ability to oversee or regulate them.
12