As you may have noticed, I tend to write lengthy introductory guides. I think it's important to not only understand how to do something, but even more importantly to understand why you're doing something and how it works. This additional knowledge allows you to not only adapt the guide to your specific situation, it also allows you to troubleshoot issues when something goes wrong. This leads to those lengthy guides where I combine not only the steps for how to do something, but also the background information necessary to understand why you're doing it.
This is a companion discussion topic for the original entry at https://engineerworkshop.com/devlog/devjournal-2020-01-28/