{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:11:33Z","timestamp":1750306293808,"version":"3.41.0"},"reference-count":0,"publisher":"Association for Computing Machinery (ACM)","issue":"9","license":[{"start":{"date-parts":[[2015,11,1]],"date-time":"2015-11-01T00:00:00Z","timestamp":1446336000000},"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":[[2015,11]]},"abstract":"<jats:p>Dear KV, Why are so many useful features of open-source projects hidden under obscure configuration options that mean they\u2019ll get little or no use? Is this just typically poor documentation and promotion, or is there something that makes these developers hide their code? It\u2019s not as if the code seems broken. When I turned these features on in some recent code I came across, the system remained stable under test and in production. I feel that code should either be used or removed from the system. If the code is in a source-code repository, then it\u2019s not really lost, but it\u2019s also not cluttering the rest of the system. Use It or Lose It<\/jats:p>","DOI":"10.1145\/2857274.2897034","type":"journal-article","created":{"date-parts":[[2019,5,16]],"date-time":"2019-05-16T15:01:36Z","timestamp":1558018896000},"page":"26-32","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Code Hoarding"],"prefix":"10.1145","volume":"13","author":[{"given":"George","family":"Neville-Neil","sequence":"first","affiliation":[]}],"member":"320","published-online":{"date-parts":[[2015,12,21]]},"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2857274.2897034","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/2857274.2897034","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T04:39:08Z","timestamp":1750221548000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2857274.2897034"}},"subtitle":["Committing to commits, and the beauty of summarizing graphs"],"short-title":[],"issued":{"date-parts":[[2015,11]]},"references-count":0,"journal-issue":{"issue":"9","published-print":{"date-parts":[[2015,11]]}},"alternative-id":["10.1145\/2857274.2897034"],"URL":"https:\/\/doi.org\/10.1145\/2857274.2897034","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2015,11]]},"assertion":[{"value":"2015-12-21","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}