{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,7,30]],"date-time":"2025-07-30T14:26:12Z","timestamp":1753885572545,"version":"3.41.2"},"reference-count":0,"publisher":"Association for Computing Machinery (ACM)","issue":"6","license":[{"start":{"date-parts":[[2007,9,1]],"date-time":"2007-09-01T00:00:00Z","timestamp":1188604800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2007,9]]},"abstract":"<jats:p>A recent conversation about development methodologies turned to the relative value of various artifacts produced during the development process, and the person I was talking with said: the code has \"always been the only artifact that matters. It\u2019s just that we\u2019re only now coming to recognize that.\" My reaction to this, not expressed at that time, was twofold. First, I got quite a sense of d\u00e9j\u00e0-vu since it hearkened back to my time as an undergraduate and memories of many heated discussions about whether code was self-documenting. Second, I thought of several instances from recent experience in which the code alone simply was not enough to understand why the system was architected in a particular way.<\/jats:p>","DOI":"10.1145\/1317394.1388789","type":"journal-article","created":{"date-parts":[[2020,4,1]],"date-time":"2020-04-01T15:26:21Z","timestamp":1585754781000},"update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Only Code Has Value?"],"prefix":"10.1145","volume":"5","author":[{"given":"Terry","family":"Coatta","sequence":"first","affiliation":[{"name":"Vitrium Systems"}],"role":[{"role":"author","vocabulary":"crossref"}]}],"member":"320","published-online":{"date-parts":[[2007,9]]},"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1317394.1388789","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T13:39:17Z","timestamp":1750253957000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1317394.1388789"}},"subtitle":["Even the best-written code can\u2019t reveal why it\u2019s doing what it\u2019s doing."],"short-title":[],"issued":{"date-parts":[[2007,9]]},"references-count":0,"journal-issue":{"issue":"6","published-print":{"date-parts":[[2007,9]]}},"alternative-id":["10.1145\/1317394.1388789"],"URL":"https:\/\/doi.org\/10.1145\/1317394.1388789","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2007,9]]},"assertion":[{"value":"2007-09-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}],"article-number":"1317394.1388789"}}