Flow General Notes

As of writing this page, December 12th 2021, Flows are very much on their way to be the primary source of automation on the Salesforce platform.
They will undoubtedly fully replace Process Builder within roughly a year, and will probably be made to replace Workflows and Approval Processes after that, I would guess within the next 3 years.

Most of the advanced administrators will welcome this change. After all, Flows are more powerful than anything else, and are more maintainable than Process Builder (learning curve notwithstanding).
They do however introduce quite a few problems that were previously hidden from the Administrator, such as looping and bulkification. This isn't bad per se, but it adds yet another level of complexity to administrator knowledge. 
To reference the diagrams in the official Architect Decision Guides, things are getting easier to break while adding more functionality.

So what we're saying in this introduction is If you are an Administrator looking at these pages for help with an automation without knowing much about Flows, please take a moment to review how you might break stuff when/if it fails.

As a final quick introductory paragraph, yes we know these Conventions are much more annoying to follow than the ones for Process Builder and Fields. This is because Flows are more complex. Please remember that we try to make these only as annoying as needed and as lean as possible.

_{Bonus useless knowledge: Flows themselves are just an old technology that Salesforce released in 2010: Visual Process Manager. That itself is actually just a scripting language: “The technology powering the Visual Process Manager is based on technology acquired from Informavores, a call scripting startup Salesforce bought last year.” (2009) Source}