You're arguing against a strawman. The author didn't say "Throw out all your old tools, sysadmins, and rewrite them in Go"
But he is saying: ignore the team, ensure your job position increasing the bus factor, ignore security updates best practices. Among other things.
What I said was that I, personally, am going to be writing more personal tooling in Go. I was pretty clear that our team is NOT switching off Python. It's in the last section entitled "This isn't a switching story"
Even I'm thinking to dedicate some spare time to explore Go thanks to some articles I've seen in the late days.
Next time I will try to be more in line with what is being said.
Thanks for reading, understanding and clarifying.