I (ab)use gfycat. #!/bin/sh curl -s -X POST "https://api.gfycat.com/v1/gfycats" -H "Content-Type: application/json" | exec jq .gfyname -r It generates a n

I (ab)use gfycat. #!/bin/sh curl -s -X POST "https://api.gfycat.com/v1/gfycats" -H "Content-Type: application/json" | exec jq .gfyname -r It generates a name like HardDisastrousJaguar. Thus far, all other code name formats seem to suck -- e.g. they're 12 words, they don't start with adjectives and end with nouns, etc. So the trick is to map a specific continuous release back to a name like HardDisastrousJaguar. Any ol' database would do the trick. And the best database is the code release itself; you can throw the above code into your continuous release process to generate a unique name during the release. But, like you, I would love it if there was a way to map 160 bits to a name like HardDisastrousJaguar without relying on external services. Unfortunately, us nerds seem to get caught up on correctness ("There might be collisions! We need 12 words for 160 bits!") while losing sight of the fact that it's supposed to be for humans to read. HardDisastrousJaguar is memorable; <12 random english words> is better than 160 random bits, but it's a long way from HardDisastrousJaguar.