Writing or modifying either program, the explicit Go one and the automagical Python one, requires reading and understanding exactly the same amount of etcd docu

Writing or modifying either program, the explicit Go one and the automagical Python one, requires reading and understanding exactly the same amount of etcd documentation: both programs are going to perform the same computations with the same parts of the JSON structure. If etcd changes its file format or API, both programs break in the exact same way. Fixing the Go program requires adjusting boilerplate code that the Python program doesn't have, but it's unlikely to be difficult. Comments and names in the Go example summarize etcd documentation and API for no good reason, creating significant ambiguity and an unnecessary maintenance burden. The only point of authority is etcd documentation, not client code. The "uh" programmer in the example is a strawman and an idiot. Remotely professional real people read documentation instead of guessing or making assumptions; no significant skills are required.