I once spent an inordinate amount of time with a friend of mine, who I consider to be a master of recording & sound engineering. He has been at it for decades, paid his dues, and worked with some greats. He executes his craft with the utmost care and caring... (something I have come to realize is what separates the true pros from the learned hacks). Anyway, I remember watching him in do his thing in the studio as I assumed the role of a quiet observer. Despite his obvious adeptness and ingenuity, he would always play the part of the Absent-Minded Professor, as opposed to the James Bond smooth-operator type. I think it was partly a schtick to make people feel more at ease, but there was a genuineness and willingness to be vulnerable, as though allowing himself to be human probably made the job less fatiguing. I distinctly remember my favorite phrase of his. On a couple of occasions, while turning knobs and fixing some problem, in a wonderous voice he would declare, "so much to know..."
It's stuck with me because it's true about so many things, no matter how much of a master of your craft you are - there is always more to know. So much more. I've worked in IT and done various software development for about 30 years now, and yet that's been the theme for me lately - as I try to wrap my head around newer (to me) concepts such as containerization, full stack application development, and more. I should have started learning these things about 10 years ago, so I have to play catch up. But it's enough to make me feel old.
Anyway, follow along as I may post some perspectives on (but not limited to) the following concepts, as I learn them:
- Kubernetes Clusters, K3S for high availability scalability, management thereof
- Tying all this together: MicroSaaS development and deployment