That's a Lot of YAML

This is my favourite turd: - 07 - 08 Results in [ 7, "08" ] due to assumptions about octal and strings. This assumption was discovered deep within some templated YAML generated by templated something else three levels down and resulted in a complete k8s cluster failure for us, but only the 08 cluster! It worked in the first 7.

A respected senior engineer once told me "all configuration is code, if it modifies the behaviour of software, it needs to be testable" Yaml is huge unintuitive PITA, I recently spent multiple hours figuring out the best way pass CLI arguments to a k8s cronjob via yaml. I only managed to solve the weird error messages after I stumbled upon the stackoverflow post linked in the webpage https://stackoverflow.com/a/21699210 > There are NINE (or 63*, depending how you count) different ways…

Yaml is the language nobody needed. All we wanted was a better JSON format that supports comments and doesn’t crash with an extra comma as the end of a list, eg: [1,2,3,]

Because of how most text tools work, even something like copy and paste, I personally avoid any language which uses whitespace for its syntax. I imagine one day I will use Python, and I've already an idea of what syntax style I will use. It will look like this: def SomeFunction (firstArgument, argumentTheSecond): #{ WriteLog("SomeFunction(", firstArgument, argumentTheSecond, ")")#; print("Hello, World!")#; #} This way, if I ever have to copy and paste it, and the whole thing gets de-indented, I am…