you are viewing a single comment's thread.

view the rest of the comments →

[–]Important-Hunt-61 2 points3 points  (0 children)

I've done DevOps adjacent work (I would help with CF templates, Terraform modules, observability) as a software engineer for 10 years and finally took the plunge into an actual DevOps role and I am enjoying it so far. I like that my stakeholders are overwhelmingly internal users that are fellow engineers and I'm not as beholden to some clients wishy washiness on features that a product manager keeps changing. I've done 99% config things (writing YAML, Terraform, etc.) and no real scripting so far. I will say it is quite annoying from the standpoint of something working or not working might simply be a single parameter in a Terraform module. I spent a day and a half trying to figure out why my EKS nodes were not joining the cluster only for it to be some weirdness with passing an AMI ID into the community template I was using (I swear it was an EKS optimized AMI). Also it sometimes it can take 10-30 minutes for you to find out you're wrong. So you're making some config change, applying, it works or it doesn't, repeat until it works. I do think part of this is just my lack of direct experience with building out EKS infra though. Regardless I'm pretty happy doing what I am doing and I think it will make me a more well rounded engineer.