STFU: Shut The Flow Up! How To Think Through Flow Architecturally

This session is trying to carve an opinionated pathway of how to efficiently organize and maintain your flows. Flows have inherited an architectural principle that might not be optimized for its use case – mainly that of “one process per object”. I will interrogate this concept, go over what parts are still good (if any) of this paradigm, then proffer some ideas on the best way to architecturally address your automation needs vis-a-vis flow. There will be discussion of mixing and matching, tooling, and general stylistic concerns, among others. By the end of the presentation, users should have an understanding about how I would address flow architecture and in turn, this should be a spring board for further discussion and a jumping off point for their own thoughts.