Vision for a Modern Software Workflow

We’ve heard the generalities: “shift left” for cheaper bug resolution or “avoid work-in-progress” for more efficient development. How do those mix? What is the role of the software workflow, and how do we think about optimization to our workflow holistically? In order to tackle those weighty questions, we’ll dive into a few of the ideas that I’ve found to be axiomatic in such matters. This will allow us to look at specific cases of workflow changes that went poorly, and start to build tools for reasoning about the value and applicability of changes to testing strategy, code review, static analysis, etc.