{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T04:28:06Z","timestamp":1750220886880,"version":"3.41.0"},"reference-count":0,"publisher":"Association for Computing Machinery (ACM)","issue":"5","license":[{"start":{"date-parts":[[2019,10,1]],"date-time":"2019-10-01T00:00:00Z","timestamp":1569888000000},"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":[[2019,10]]},"abstract":"<jats:p>Unless what you are processing, storing, or transmitting are, quite literally, strings that come from and are meant to be shown to humans, you should avoid processing, storing, or transmitting that data as strings. Remember, numbers are for computers, strings are for humans. Let the computer do the work of presenting your data to the humans in a form they might find palatable. That\u2019s where those extra bytes and instructions should be spent, not doing the inverse.<\/jats:p>","DOI":"10.1145\/3371595.3379349","type":"journal-article","created":{"date-parts":[[2020,1,13]],"date-time":"2020-01-13T21:04:57Z","timestamp":1578949497000},"page":"34-38","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Numbers Are for Computers, Strings Are for Humans"],"prefix":"10.1145","volume":"17","author":[{"given":"George V.","family":"Neville-Neil","sequence":"first","affiliation":[]}],"member":"320","published-online":{"date-parts":[[2020,1,13]]},"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3371595.3379349","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3371595.3379349","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,17]],"date-time":"2025-06-17T23:44:23Z","timestamp":1750203863000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3371595.3379349"}},"subtitle":["How and where software should translate data into a human-readable form"],"short-title":[],"issued":{"date-parts":[[2019,10]]},"references-count":0,"journal-issue":{"issue":"5","published-print":{"date-parts":[[2019,10]]}},"alternative-id":["10.1145\/3371595.3379349"],"URL":"https:\/\/doi.org\/10.1145\/3371595.3379349","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2019,10]]},"assertion":[{"value":"2020-01-13","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}