Should you move fast and break things?

Facebook started in 2004 with the passionate motto "Move fast and break things". (Mark Zuckerberg was nineteen years old.)

Zuckerberg stated five years later, in 2009, that "unless you are breaking stuff, you are not moving fast enough."

Fast enough for what? He didn't say.

In 2014, the company changed its motto to "Move fast with stable infrastructure". As if to say: move as fast as possible, but please let's keep things intact.

The speed is not the focus anymore.

How many fundamental things were probably broken in those ten years? Imagine how fragile the infrastructure was, after a whole decade of accepting the high costs of mending stuff as a fair price for "quick" shipments.

Move fast, spend more?

Mending careless done stuff means more time and money spent on development and QA. This means outdated documentation, confused managers, frustrated devs, and lost users.

This "gotta go fast" philosophy puts a lot at risk, including web security, client communication, and consumer satisfaction. Even human lives are at stake, in businesses like health and aviation.

So the best places to work (and to buy from) are the ones that invest in monitoring, prevention, automation, and documentation. No-code tools make it easier for businesses of all sizes.

Can work in tech be fast but also stable, minimizing risks? If yes, tell me in the comments: at what cost?

Get the free version of suittest, the No-Code Test Automation Tool.