In this talk, see how Betterment is leveraging DCM with a few case studies and find out how your team can also accelerate dev time with robust linting. Betterment uses DCM's built in lints and custom DCM lints to move bugs into loop #2. As a result we: - Ship faster - Ship higher quality - Have to rely less on tests and manual QA Errors can be caught at many different layers in the development loop (not necessarily exhaustive): 1. IDE auto-complete 2. IDE surfaced static errors and lint warnings 3. Runtime errors in sandbox/staging 4. Tests 5. Code review 6. QA 7. Production crash logs 8. User feedback/reviews The further into the loop an error gets, the more developer time is wasted and the slower your feature velocity will be. Errors that get to the end of the loop become user facing and directly impact business outcomes.