Please invite me over. I am SO into a nice, quiet nap (something I've loved since my early 30's) and that really sounds great. 
This ^^^
I'm pretty much there right now. Home has been humming along w/out any significant issues. You know you're in trouble (i.e., things are too quiet) when you look forward for low battery notifications so you aren't so "Captain Dunsel-ish."
Funny, I am absolutely not a napper. If I take a nap, the rest of the day is shot... I never really wake back up, I just want to go back to sleep 
My SO takes naps daily, and very seriously 
I also had to make sure that the Roborock vac doesn't start cleaning during her nap time, so Nap Time disables that too, and reschedules bedroom cleaning for later. I remember that day the vac started during her nap... 
I generally agree with a bunch of this, and I come from a computer science background, and even then, when I started it took awhile to understand Apps versus Drivers (& devices with Child devices) and virtual devices.
Initially, that just wasn't clear to me, even reading the documentation - To me, that was a bump in the initial learning curve - I came from ST (and X10 before that), so devices and even pairings made sense - But the "automagical fingerprinting" driver type selection (which is sometimes wrong) wasn't clear, and switching to "device" having to clean up the wrong selection, manual set the correct driver type, configure and/or initialize, all that seemed a bit much initially.
The next mental hurdle (at least for me), was understanding the difference between system and 3rd party/community apps and drivers, and learning that HPM is out there. And even in the system Apps, there is a lot of overlap between "similar" things, where some have been deprecated, and new apps are where current development is happening etc. IMHO, some should be marked with [Legacy] or something, as when you don't know what any of them do, it's easy to go down the rabbit hole.
Finally, debugging any network issue (for me, it was Z-Wave ghosts, and power reporting settings on a plug) fortunately didn't happen till several months in. - But reading the forums, I see that repeatedly with new users, and either WiFi issue, or Zigbee channel issues, or Z-Wave ghosts - Personally, I find Matter much cleaner and it just works, but clearly that's not everyone's experience. - It just seems like you get the 1st few devices working, then there is some network issue with any of network protocols, and it's really a black box (or you need to add 3rd party plug in's etc to stand a chance at debugging).. It just would be nicer if there was better troubleshooting tools in a single place, versus logs, versus Zigbee logs, versus Z-Wave mesh details, etc.. Not sure that I know what I would put in such a main "troubleshooting tab", but understanding what's where, can be a challenge for a new user.
Just my two cents, beyond the obvious bits like if/then/else logic and IP networking 101
Finally, there are a bunch of subtle watchouts as it relates to concurrence, multi-threaded code in RM, but that's all somewhat of a more advanced topic, for later headaches.. - And then there are considerations around Web-Core (versus RM)
Then external links to HA, AppleHome, Node-Red, etc, etc. - Perhaps I need to write a book..
https://www.amazon.com/Complete-Hubitat-Elevation-User-Guide-ebook/dp/B0FH793H1Z
https://www.amazon.com/MASTERING-HUBITAT-ELEVATION-2-3-4-Step-ebook/dp/B0FZFVW5YR
I would add: Keep it simple. Not necessarily the entirety of automations. But keep each moving part as simple as possible.
Long, long ago I worked for a company that still stored a lot of their mission-critical data on magnetic tape. There was one set of data that lived on 5 or 6 reels of tape. The data had to be processed daily, and there wasn't enough time during the batch-processing window to read the data more than once. So every single system that needed to access that data lived in one single very, very large COBOL program. There was one man whose entire job was the care and feeding of that one program. I'm sure the folks in the C suite lived in fear something would happen to him. Periodically there was a project to modernize the data and move it into a directly accessible database. But the project never really got off the ground because nobody knew all that program did. And it was so convoluted and full of spaghetti code that it was almost impossible to analyze it.
Rule Machine can be like that. When I first started playing around with RM, I had one very large rule that did almost everything I could think of. It got so big that I couldn't edit it because trying to open it crashed the interface. Then someone reminded me that rules are free, and now I have lots of them.
So what I'm saying is... don't be like newbie me or that long-ago nameless company. Rules are free. Make lots of them, and keep them simple. It makes figuring out what's happening so much easier.
Good advice. I would also recommend developing a strategy for naming your rules and devices, so that you can more easily find the one that's going south when something goes south.
I've seen a number of such strategies documented here, but I think everyone develops their own that makes the most sense to them.
Likely mentioned already.... But I decided to add it to my initial post:
EDIT...
I would add posting here on the Community and doing so early on in your journey... Too often we see people pleading for help well after they have reached a point of frustration and disappointment, when a simple question early on could have saved them hours of time unsuccessfully attempting to troubleshoot their issue. There is no competition here, there are experienced automation experts here happy to help.
I check the community page almost every day. I've learned a lot and run across interesting post like this.
This thread is a great idea. Can it be made into a Wiki or some post where this thread can be distilled into one intro read for beginners?
And join the Hub Owners Group to enable posting pictures and or screenshots of anything you think might be helpful.
As easy as:
Windows key plus the Shift key plus the S key to snip a pic.
Control key plus the V key to add it to your post.
If you want to keep things compact.
Triple click the image link.
Then click on the Gear icon, select Hide Details.
And if desired, double click the default Summary label to change it something descriptive.
Download the Hubitat app
