{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:08:16Z","timestamp":1750306096318,"version":"3.41.0"},"reference-count":5,"publisher":"Association for Computing Machinery (ACM)","issue":"5","license":[{"start":{"date-parts":[[2017,10,1]],"date-time":"2017-10-01T00:00:00Z","timestamp":1506816000000},"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":[[2017,10]]},"abstract":"<jats:p>Successful pranks require care and planning. Write a design proposal and a project plan. Involve operations early. If this is a technical change to your website, perform load testing, preferably including a \"dark launch\" or hidden launch test. Hide the prank behind a feature flag rather than requiring a new software release. Perform a retrospective and publish the results widely. Remember that some of the best pranks require little or no technical changes at all. For example, one could simply summarize the best practices for launching any new feature but write it under the guise of how to launch an April Fools\u2019 prank. That would be hilarious.<\/jats:p>","DOI":"10.1145\/3155112.3171529","type":"journal-article","created":{"date-parts":[[2018,2,13]],"date-time":"2018-02-13T15:40:40Z","timestamp":1518536440000},"page":"12-23","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":0,"title":["Operational Excellence in April Fools\u2019 Pranks"],"prefix":"10.1145","volume":"15","author":[{"given":"Thomas A.","family":"Limoncelli","sequence":"first","affiliation":[{"name":"StackOverflow"}]}],"member":"320","published-online":{"date-parts":[[2017,10]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"Dumke-von der Ehe B. 2015. The making of StackEgg; http:\/\/balpha.de\/2015\/04\/the-making-of-stackegg\/.  Dumke-von der Ehe B. 2015. The making of StackEgg; http:\/\/balpha.de\/2015\/04\/the-making-of-stackegg\/."},{"key":"e_1_2_1_2_1","unstructured":"Kottasova I. 2016. Google's April Fools' prank backfires big time. CNNtech; http:\/\/money.cnn.com\/2016\/04\/01\/technology\/google-april-fool-prank-backfires\/index.html.  Kottasova I. 2016. Google's April Fools' prank backfires big time. CNNtech; http:\/\/money.cnn.com\/2016\/04\/01\/technology\/google-april-fool-prank-backfires\/index.html."},{"key":"e_1_2_1_3_1","unstructured":"Pike K. 2017. Stack Overflow unveils the next steps in computer security. Stack Overflow Blog; https:\/\/stackoverflow.blog\/2017\/03\/30\/stack-overflow-unveils-next-steps-computer-security\/.  Pike K. 2017. Stack Overflow unveils the next steps in computer security. Stack Overflow Blog; https:\/\/stackoverflow.blog\/2017\/03\/30\/stack-overflow-unveils-next-steps-computer-security\/."},{"key":"e_1_2_1_4_1","unstructured":"Rossi C. 2011. Pushing millions of lines of code five days a week. Facebook; https:\/\/www.facebook.com\/video\/video.php?v=10100259101684977.  Rossi C. 2011. Pushing millions of lines of code five days a week. Facebook; https:\/\/www.facebook.com\/video\/video.php?v=10100259101684977."},{"key":"e_1_2_1_5_1","unstructured":"Stack Exchange Network Status. 2015. Outage postmortem: March 31 2015; http:\/\/stackstatus.net\/post\/115305251014\/outage-postmortem-march-31-2015.  Stack Exchange Network Status. 2015. Outage postmortem: March 31 2015; http:\/\/stackstatus.net\/post\/115305251014\/outage-postmortem-march-31-2015."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3155112.3171529","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/3155112.3171529","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T03:30:28Z","timestamp":1750217428000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/3155112.3171529"}},"subtitle":["Being funny is serious work."],"short-title":[],"issued":{"date-parts":[[2017,10]]},"references-count":5,"journal-issue":{"issue":"5","published-print":{"date-parts":[[2017,10]]}},"alternative-id":["10.1145\/3155112.3171529"],"URL":"https:\/\/doi.org\/10.1145\/3155112.3171529","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2017,10]]},"assertion":[{"value":"2017-10-01","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}