Please avoid mega-flows!
Again: the real issue lies not in flows per se, but in the use of overly complex "mega-flows," which are unwieldy and hard to maintain.
That point was made in this article as best practice #3 :
https://lnkd.in/gM2n6ar2
And then there's the misconception that flows can completely eliminate the need for developers in an organization. While flows are great for simple, lightweight tasks, developers are still essential for more complex, critical logic that flows aren't designed to handle.
("Please avoid M.A.D. flows" is the last page "sponsor" of the October edition of the Cloud Chaser Almanac to be published in a few hours. 😂)
