How about music as code…Sonic-Pi would like to offer a counterpoint :)
Re:Diagrams · Diagram as Code
by CactusOnFire on Monday November 04, 2024 @08:57PM
(#42047972)
I think the counter-point to that would be that if you're writing infrastructure as code, and your architects are using a specific language anyways (Python in this case), it makes more sense for data governance and editing reasons to just keep things in the existent ecosystem and not worry about having to procure another license.
Vs. Cooking or Writing which aren't coding practices unto themselves.
Re:Diagrams · Diagram as Code
by alanbernstein on Tuesday November 05, 2024 @01:47AM
(#42049167)
Recipes absolutely should be written in code. If I could view source, copy the recipe yaml, and paste into my personal recipe manager app, it would be much more convenient.
Screenplays... are already written in code, partly. If they weren't, they'd include quotation marks and "she said" after every line.
I think this is too loose of a definition of code...
Yaml isn't really code in the same sense as python is, and Shakespeare didn't write in code in the same sense that the diagrams in this article are.
Re:Diagrams · Diagram as Code
by alanbernstein on Monday November 11, 2024 @05:45PM
(#42111130)
Well, you're right about that, but then they were your examples.
Or a screenplay?
(Because there are better formats for them)