How to be quick without being dirty: maintaining quality at high velocity

When it comes to software quality, moving faster doesn’t necessarily mean you’re in a better place, especially when you don’t have the right pipelines or processes set up. Eventually, the bugs resulting from shortcuts or poor practices outweigh the benefits of shipping fast. What are some indicators that you might be moving too fast? And how can you keep a good pace while being confident your code is stable and error-free?

When you’ve got proper safeguards in place (a good warning system, sufficient test coverage, and strong CI/CD), you can spend more time thinking about coding and less about risk. Where do you start when building out these systems? And until you have your testing and infra in place, how can you supplement that with manual QA and UAT?

You don’t always have time to implement the perfect architecture or the best-practice solution. However, once you know what matters in a dev decision, you can implement one that is almost as good in a fraction of the time.

In this talk, Erin and Benjie will talk about how to make quick, smart decisions during development so that you can move fast and not break things. They’ll discuss how you can de-risk processes so that devs don’t have to supervise every new deployment. And they’ll talk about how you can deconstruct workflows to promote developer productivity holistically.