In training, I recommend the following in ~/.vimrc:
autocmd FileType yaml setlocal ai ts=2 sw=2 et nu colorcolumn=1,3,5,7,9,11,13
But use a good editor! (Atom,. Visual Studio Code, Sublime, etc)
Also, I keep my playbooks in separate directories (see screenshot), and every playbook is called playbook.yml in order to take better advantage of searching through my command history when using ansible-playbook playbook.yml and ansible-playbook --syntax-check playbook.yml
I always encourage my students to "tell the story of your playbook" i.e. articulate their playbook goals in point form. Those then become the names of your tasks.
In response to a VT class request, I created https://gitlab.com/rgdacosta/sync-work which uploads their class created playbooks to the cloud, so that they could download them from their physical machines. I opened vim, and told the story of my playbook in front of them, then noted the modules which I thought would best satisfy my task goals, then figured out the specifics offline. They enjoyed that!
Parametize your playbooks - keep them as dynamic as you can.
When creating your playbook consider creating the associated undo or rollback tasks and tag them accordingly.
Have a style guide that specifies how you do things, from using variables, to how you declare booleans, to the use of includes. Have guidelines as to how playbooks ought to be written.
Always keep your playbooks under version control!
And that leads me to my last point, always give examples which are not covered in the courseware - add value. Exposure to scenarios is important - add value!
