The post claims to have "better hames" for the AWS services. Many of those names are much worse.

Take the suggested "Amazon Beginning Cut Pro" which was their suggestion for "Elastic Transcoder".

"Beginning Cut Pro" is clearly a reference to Apple's NLE, Final Cut Pro. I would suggest that there are literally zero people on the planet, who would use Amazon's video transcoding service (I imagine it's essentially a distributed ffmpeg queue.) to process video files before importing them into FCP.

This isn't "tongue in cheek", this is "stupid and confusing as an attempt at a laugh". I mean, what if I suggested that a hosted Memcached service be called AppStart because it uses memory and Apps use memory.

> having something to translate back to things I can understand was really helpful

My issue is that several of the services covered, already have a MORE MEANINGFUL name. So if I had no idea what "Elastic Transcoder" did, but it was instead called "Amazon Beginning Cut Pro", I would then assume it's somehow a tool meant to work with FCP, and disregard it (I don't need a NLE, at most maybe I need something akin to ffmpeg, so I can transcode/scale video files between formats automatically and efficiently.

If it's comedy, call it comedy, and make it actually funny.

If it's meant to be a useful guide, make it fucking accurate, or it's worse than what AWS is doing already.