This isn't meant as a rant if it comes off as such.
I just experienced my first bad flow pinning my flow count, and now i am out for the month.
I have since read many peoples confusion or complaint about how flow counts. A benfit of Flow is that MS's servers are online 24/7.
But I don't always need that. I could build and run my flows from my desktop just fine (in fact via script and task manager I do, and it costs me nothing). Flow could empower so many more people if it werent for some of these ridiculous
Flow is also a bit user centric, if I get canned and my account is turfed my flows die with them (perhaps this has been addressed). I bring it up because it illustrates there are personal flows and corporate flows.
Perhaps flow could learn from the power BI model. i.e. I build personal flows locally and then publish those that have a more enterprise need. My flow count is driven off what I automate online. And I learn how to build better flows more frequently because I have ready and easy access locally. I can also dry run my flows locally before I publish them to make sure they dont kill my counts.
Perhaps i am just extremely ignorant, this already exists in some form, and I haven't RTFM. ... on that, more training material would be lovely.