3 ms·

May have multiple reasons: 1) Some people just like the infra work, so they presume everyone likes as well. AWS eliminates/simplifies a good portion of it. 2

May have multiple reasons: 1) Some people just like the infra work, so they presume everyone likes as well. AWS eliminates/simplifies a good portion of it. 2) Some feel a sense of superiority saying they can pull off an entire infra on Hertzner. They know many younger engineers can't, since they started with AWS in mind. 3) AWS has a terrible reputation as an employer. Perhaps some these anti-AWS blog writers might have worked there, know someone who did, or heard one of the AWS PIP horror stories...

mulmboy 5y ago
Interesting take, > Some people just like the infra work I think AWS improves infra work. Using CDK is a joy - primarily because it's clean, simple, and reproducible once you have stuff up and running. But the process of getting stuff up and running is its own kind of drug, it's a serious puzzle (unless you really really know what you're doing) which I find really rewarding to solve. I'm a pig in mud with CDK. Compare that with traditional infra work and I immediately start to worry about how to make sure that everything is provisioned correctly, that other people on the team aren't messing things up, how I'm going to implement zero-trust type auth without something akin to IAM, how I'm going to implement monitoring without the monitoring system becoming its own beast....
- rmbyrro 5y ago
  Absolutely. I'm referring to the traditional infra work. I think these people should seek a job at AWS, Azure, GCP.
randomtwiddler 5y ago
I avoid it because of unsafe billing practices. As someone higher up in the comments said, "don't buy stuff you can't afford". The problem there is understanding AWS billing is an industry itself. Numerous stories of people who thought they understood something they didn't. Software bugs resulting in bankrupty. I have to have billing predictability out of my service provider. I'm not aware of AWS employment issues other than it being a place to burn you out, but the wearhouse side has had plenty of newsworthy incidents.

mulmboy 5y ago

Interesting take, > Some people just like the infra work I think AWS improves infra work. Using CDK is a joy - primarily because it's clean, simple, and reproducible once you have stuff up and running. But the process of getting stuff up and running is its own kind of drug, it's a serious puzzle (unless you really really know what you're doing) which I find really rewarding to solve. I'm a pig in mud with CDK. Compare that with traditional infra work and I immediately start to worry about how to make sure that everything is provisioned correctly, that other people on the team aren't messing things up, how I'm going to implement zero-trust type auth without something akin to IAM, how I'm going to implement monitoring without the monitoring system becoming its own beast....

rmbyrro 5y ago
Absolutely. I'm referring to the traditional infra work. I think these people should seek a job at AWS, Azure, GCP.

randomtwiddler 5y ago

I avoid it because of unsafe billing practices. As someone higher up in the comments said, "don't buy stuff you can't afford". The problem there is understanding AWS billing is an industry itself. Numerous stories of people who thought they understood something they didn't. Software bugs resulting in bankrupty. I have to have billing predictability out of my service provider. I'm not aware of AWS employment issues other than it being a place to burn you out, but the wearhouse side has had plenty of newsworthy incidents.