So, here I am, trying to fill in the gaps and fully understand why x chose configuration y. I can’t complain about this practice, after all, whatever the format, a blogger is doing this for the benefit of others, mostly without tangible benefit and often their focus is on a concept or demonstrating something briefly and simply so others can quickly understand the benefits. This is due to my own ignorance I know, but it’s still frustrating. I’m pained by losing focus and having to do extra work before I can fully understand what’s being discussed and covered in a piece I’m reading. One reason I enjoy and appreciate Larry’s posts is that (mostly) he doesn’t skip over the low level detail a refreshing change from the common practise of referring to another post the author has written, someone else’s posts entirely or a documentation website somewhere. I may be debating the benefits and drawbacks of an automated (no I don’t mean DevOps) approach to networking entirely but regardless, it’s the most complete series of posts out there I know of.
I’m particularly enjoying the Hey, I can DevOPS my Network too! series by Larry Smith Jr. at the moment. There’s been a whole heap (programming pun intended) of blogs around automation and virtualisation over the last few years, with some rather good ones of late centred around the now classic mix of VirtualBox, Vagrant and Ansible*|**.
0 kommentar(er)
