particularly move your cv to the blank email
You must log in or register to comment.
“we’ve had one break fast, yes. What about second break fast?”
Do you work in devops?
Dev oops
I believe we call that a “fast follow”.
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.
It 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.
but what about the auto tests
Management 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
“They were always green”. I wish
“also, there was only ever one and it just asserts true”
Developers are responsible for their own testing.
Test coverage and end to end tests will be assigned to someone no longer at the company, or on vacation.
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.
come to think of it, at this company devs aren’t needed, just QAs and a toxic manager would suffice
oh, that’s how you end up with
APERTURE SCIENCE
