3 ms·

Yes, you as a developer should know something about how the service works before you use it. I first opened the AWS console in 2016 and by then I had read abou

Yes, you as a developer should know something about how the service works before you use it. I first opened the AWS console in 2016 and by then I had read about the possible gotchas.

earnesti 1y ago
Well, people get informed by reading these stories. So let's keep informing people to avoid AWS.
- JustExAWS 1y ago
  Yes I’m sure large corporations and even startups are going to leave AWS because a few junior devs didn’t do their research.
  - crote 1y ago
    You do know that large corporations and startups employ junior devs as well, right? All else being equal, would you rather choose the platform where a junior dev can accidentally incur a $1M bill (which would already bankrupt early startups), or the platform where that same junior dev get a "usage limits exceeded - click here to upgrade" email?
    - JustExAWS 1y ago
      Well, first I wouldn’t give a junior dev with no experience admin rights to an AWS account and would I have tight guardrails around what they can do - like I’ve done now with over a dozen implementations for clients since I’ve been in consulting for five years and the four years before that as an architect for product companies. I also wouldn’t give a junior dev access to production databases. Also from working with AWS from both the inside (Professional Services) and the outside at a third party consulting companies, I know how aggressively AWS is about keeping startups and they would never risk losing the continuing revenue of a company like that.
    - dragonwriter 1y ago
      > All else being equal, would you rather choose the platform where a junior dev can accidentally incur a $1M bill If a junior dev has the access to do that, then there is a big failure (probably more than one) by someone who isn't a junior dev after choosing AWS that was necessary to enable that.

3 ms·

Yes, you as a developer should know something about how the service works before you use it. I first opened the AWS console in 2016 and by then I had read abou

by JustExAWS 1y ago

Yes, you as a developer should know something about how the service works before you use it. I first opened the AWS console in 2016 and by then I had read about the possible gotchas.

earnesti 1y ago
Well, people get informed by reading these stories. So let's keep informing people to avoid AWS.
- JustExAWS 1y ago
  Yes I’m sure large corporations and even startups are going to leave AWS because a few junior devs didn’t do their research.
  - crote 1y ago
    You do know that large corporations and startups employ junior devs as well, right? All else being equal, would you rather choose the platform where a junior dev can accidentally incur a $1M bill (which would already bankrupt early startups), or the platform where that same junior dev get a "usage limits exceeded - click here to upgrade" email?
    - JustExAWS 1y ago
      Well, first I wouldn’t give a junior dev with no experience admin rights to an AWS account and would I have tight guardrails around what they can do - like I’ve done now with over a dozen implementations for clients since I’ve been in consulting for five years and the four years before that as an architect for product companies. I also wouldn’t give a junior dev access to production databases. Also from working with AWS from both the inside (Professional Services) and the outside at a third party consulting companies, I know how aggressively AWS is about keeping startups and they would never risk losing the continuing revenue of a company like that.
    - dragonwriter 1y ago
      > All else being equal, would you rather choose the platform where a junior dev can accidentally incur a $1M bill If a junior dev has the access to do that, then there is a big failure (probably more than one) by someone who isn't a junior dev after choosing AWS that was necessary to enable that.