3 ms·

I'll take names over alphabet soup. My EBS EC2 machines are not playing nicely with ELB (but my EFS ones are), I think it might be to do with EMR, or maybe EKS.

deleted 8y ago
[deleted]
rad_gruchalski 8y ago
You could always say: "My elastic block service elastic cloud compute machines are not playing nicely with elastic load balancers (but my elastic file system ones are), I think it might be to do with elastic map reduce, or maybe elastic kubernetes service." No soup.
- akuji1993 8y ago
  So much better.
- mxiia 8y ago
  so elastic!
  - rad_gruchalski 8y ago
    That's a different company!
- _verandaguy 8y ago
  It feels like English should have a provision to factor out the word "elastic" in this case. Just assume every word in the sentence is elastic.
  - kbutler 8y ago
    "My elastic block service elastic cloud compute machines are not playing nicely with elastic load balancers (but my elastic file system ones are), I think it might be to do with elastic map reduce, or maybe elastic kubernetes service." "My elastic services are not working. Cloud compute machines..."
- coliveira 8y ago
  You nailed it, I hate the tendency of english speakers, specially in tech, to use nonsense acronyms when it would be much easier and understandable to use the word itself, or at least part of it.
- raydev 8y ago
  > No soup. Yeah, what you did is more like a porridge that makes you choke.
- fredley 8y ago
  The problem is partly that AWS—sorry, Amazon Web Services—refer to their products like this in all their documentation and marketing. Using acronyms is great for brevity in communicating within closed environments (we use our own acronyms within our own office to refer to many things, including clients), but if you're product names so long-winded in the first place that you're acyronymizing them all publicly in your own materials you have a problem.
- philosopherlawr 8y ago
  No way engineers will ever do this. We're far to use to TLAs and also, it's way too long. Having a simple, metaphorical brand name allows you to then build on top of that. Can you imagine if Java had instead been called WriteOnceRunAnywhereC++Alternate instead of java? Then, we'd have the writeoncerunanywhereC++alternate Virtual Machine
  - fredley 8y ago
    WORAC. I like it.
fs111 8y ago
Everybody loves a good TLA!
mindcrime 8y ago
I think you need some ECS in that mix as well...
- dixie_land 8y ago
  Hmm interestingly they renamed that to Elastic Container Service. It used to be named kinda recursively as EC2 Container Service. [0] https://aws.amazon.com/ecs/ https://aws.amazon.com/ecs/ [1] https://aws.amazon.com/about-aws/whats-new/2014/11/13/introducing-amazon-ec2-container-service/ https://aws.amazon.com/about-aws/whats-new/2014/11/13/introd...

deleted 8y ago

[deleted]

rad_gruchalski 8y ago

You could always say: "My elastic block service elastic cloud compute machines are not playing nicely with elastic load balancers (but my elastic file system ones are), I think it might be to do with elastic map reduce, or maybe elastic kubernetes service." No soup.

akuji1993 8y ago
So much better.
mxiia 8y ago
so elastic!
- rad_gruchalski 8y ago
  That's a different company!
_verandaguy 8y ago
It feels like English should have a provision to factor out the word "elastic" in this case. Just assume every word in the sentence is elastic.
- kbutler 8y ago
  "My elastic block service elastic cloud compute machines are not playing nicely with elastic load balancers (but my elastic file system ones are), I think it might be to do with elastic map reduce, or maybe elastic kubernetes service." "My elastic services are not working. Cloud compute machines..."
coliveira 8y ago
You nailed it, I hate the tendency of english speakers, specially in tech, to use nonsense acronyms when it would be much easier and understandable to use the word itself, or at least part of it.
raydev 8y ago
> No soup. Yeah, what you did is more like a porridge that makes you choke.
fredley 8y ago
The problem is partly that AWS—sorry, Amazon Web Services—refer to their products like this in all their documentation and marketing. Using acronyms is great for brevity in communicating within closed environments (we use our own acronyms within our own office to refer to many things, including clients), but if you're product names so long-winded in the first place that you're acyronymizing them all publicly in your own materials you have a problem.
philosopherlawr 8y ago
No way engineers will ever do this. We're far to use to TLAs and also, it's way too long. Having a simple, metaphorical brand name allows you to then build on top of that. Can you imagine if Java had instead been called WriteOnceRunAnywhereC++Alternate instead of java? Then, we'd have the writeoncerunanywhereC++alternate Virtual Machine
- fredley 8y ago
  WORAC. I like it.

fs111 8y ago

Everybody loves a good TLA!

mindcrime 8y ago

I think you need some ECS in that mix as well...

dixie_land 8y ago
Hmm interestingly they renamed that to Elastic Container Service. It used to be named kinda recursively as EC2 Container Service. [0] https://aws.amazon.com/ecs/ https://aws.amazon.com/ecs/ [1] https://aws.amazon.com/about-aws/whats-new/2014/11/13/introducing-amazon-ec2-container-service/ https://aws.amazon.com/about-aws/whats-new/2014/11/13/introd...