3

Am I an asshole for not wanting to learn infrastructure/AWS?

im sure it isnt rocket science, but somewhere from within, even if I try my body rejects it will every fibre of its being

manual bare metal servers, deployment scripts and firewalls? sure im all in

Containers, k8s tied to nginx on the said server? sure

Entire end to end as long as it doesnt involve AWS? done and dusted

But add AWS/Azure to the mix and I'm oil to water 😪

Comments
  • 2
    I'm with you I'd rather spin up k8s then learn 15 proprietary services that can do the same thing
  • 1
    Only if you call yourself a devops guy, nothing wrong in just being a "dev". I know a lot of people who write amazing tools but cant deploy them to production by themselves.
    Even i hate azure to it's core, and for that matter, most of things from Microsoft, but so what.
  • 2
    If you already have a firm grasp on the whole process without vendor lock in, that's just great.

    AWS (and other providers) just make you pay in order to take some of the responsibility away from you, which from a corporate PoV, may be a sensible investment.

    I know for sure I wouldn't want to have to manually code an auto scaling fleet, for example.

    I let ec2/GCE/etc handle it for me.
  • 3
    I only have experience with AWS and I can tell you, the "throw a dashboard at everything" approach gets tiring sometimes.

    The documentation sucks, they have their own set of standards, and we as devs do crave fine-grained controls.

    Just because the management is happy looking at colorful dashboards doesn't mean it's ideal.
  • 1
    Everything you need to know about AWS in 100 seconds.

    https://youtu.be/ZzI9JE0i6Lc/...
  • 1
    I like to learn a few tricks, but indeed it isn’t rocket science. Knowing code inside out is much more valuable.
  • 0
    It’s all our destiny. But it has to be cloud agnostic. Cloud agnostic. Very important. We might build our own corporate wrapper on top of the cloud agnostic wrapper. We also feel like there is a need for hooks to allow for functionality outside the inner wrapper.

    I worked with cloud professionally off and on during the years. It is actually really, really, really great. But it has to make sense. It’s really impressive what the clouds offer now. (I have not used Google yet though)

    But it is really valuable knowledge. So, don’t push it to the side.
Add Comment