Building Out Tools 2

I'm not quite done, but I've built out some of my documentation on git. I want to build out some additional thoughts, but it's been a good exercise. It's been a good reminder of 2 notions - I'm not an expert at any of these technologies and as such I shouldn't assume I have the best tool for the job in my toolbox.

For instance, I've been recently reading about Git Attributes and smudge and clean filters. The example for using them is to tokenize secrets. While that's one way to do it, there are many different options and fully blown enterprise solutions. Sometimes the type of problem dictates the solution, others it's team norms or personal preference. Personally smudge and clean filters don't do it for me, but I'm glad to have an awareness. This has been part of an exercise to review git courses for new hires from Pluralsight, and it's been really useful to get into the weeds of what it can do, though it's dug into my normal reading time recently.

Instead of going on to the next topic in Pluralsight, I'm considering doing a deep dive into Kubernetes. I've had some recent challenges that a local k3s cluster could have been a possible solution, but I want a much better understanding than I have before I'm willing to put something in production. It's one thing to throw something up on GKE, but to build a bespoke cluster means good documentation and likely some good automation to provision new nodes at a minimum. When I first learned about Google and how they built the search using old hardware, I was curious how they pulled if off. It's not talked about as much, but that's one of the features of K8s that I find really interesting. It would bring me pleasure to build a franken-cluster, just to work out the tooling.