> This is not code you write. One could argue it's indirectly written. If I write C# that generates C#, my coworkers will generally yell at me with good reaso

> This is not code you write. One could argue it's indirectly written. If I write C# that generates C#, my coworkers will generally yell at me with good reason if the generated C# is illegible. One could also argue that the oath doesn't talk specifically about what I write. At work I will try to uphold readability when reviewing coworker's code as well when reviewing it, regardless of the fact that I did not write it myself. I would also be inclined to try and uphold readability when another program writes the code. > Does a compiler generate human-readable machine language code? It can, with the proper options and support tooling, and you probably want it to. How else are you going to debug crash dumps from the wild? pdbs are immensely useful to understanding crash dumps even without the original source code to map to. My work computer has a 1TB+ folder named "builds", serving no other purpose than to archive old releases with corresponding assets and PDBs to ensure those EXEs are easily human-readable, in turn making crash dumps easily human-readable. No other category takes up more space on my hard drives at work or at home. Even that really big one nobody tells mom about! All dedicated to keeping that stuff human-readable.