The article draws on a decade of experience in frontend engineering at Palantir, offering insights into effective testing strategies. It emphasizes that getting testing right can significantly boost engineering velocity, often doubling output. The author argues that while various developer practices typically yield incremental improvements, a well-structured testing approach can lead to substantial gains. Many teams struggle with automated tests that ultimately slow down development due to high maintenance costs, which detracts from their overall value. Two key strategies are proposed to minimize maintenance costs. First, tests should be designed to break frequently but allow for quick identification of whether a change is expected. Reducing the time needed to review and update tests can lead to faster iterations. The second strategy focuses on testing at the minimal cut. This means defining the scope of tests carefully, allowing for broad coverage without unnecessary complexity. For instance, when testing a route calculation module, it might be more effective to separate tests for route calculation and rendering, rather than combining them unnecessarily. The author stresses that the choice of what to mock in tests should be deliberate. Reducing the API surface area that tests interact with can decrease fragility and maintenance burdens. By choosing stable APIs and minimizing the complexity of interactions, teams can create a more robust testing framework, ultimately supporting faster and more confident development cycles.