undefined | Better HN

0 pointsraw_anon_11113mo ago0 comments

You did see the part that I worked at startup for 2.5 years, then worked at AWS ProServe for almost 4 and now work at a third party consulting company as a staff consultant leading cloud + app dev hybrid projects?

I turned down a job where the position was going to be created for me by a former coworker at AWS who is now a director at a well known non tech F500 company where I would be responsible for a multi year migration and modernization strategy that would have paid about 30% more than I was making at AWS.

I really hate babysitting infrastructure and lift and shifts so much I turned it down and took a job that paid the same as I was making at AWS. That’s just how much more I enjoy the hybrid cloud + app dev roles.

I deal strictly with AWS on the infrastructure side, the minute I’m working on a large assessment (those huge 50 page requirement docs) and they mention hybrid, or anything outside of AWS, I bring in someone who actually likes that stuff. As I do when I see it’s going to be a migration.

The other side of my job is to actually do hands on app dev + cloud either doing it myself for small projects or leading larger ones.

I’m also not the person who is going to be on call or monitoring, that’s for the young folks.

My last three projects were using the CDK, Terraform and CloudFormation respectively

0 comments

mancerayder3mo ago

I'm with you on the avoiding tedium, on-call and monitoring and overall Operations pieces of it.

There's an infrastructure creation aspect where you're creating automation systems and passing it along for others to maintain. I personally think that's a sweet spot.

Everything you said here I relate to, it seemed like you were arguing that infrastructure design and systems engineering is just "app dev ++" as opposed to a collection of skill sets that take years to learn.

It's no different than AI slop if someone thinks cloud automation is just another programming framework to learn. I've worked exactly in 0 companies that got it right when it came to intelligently designed, bullet proof systems. Some of the slop and chaos is so bad it takes big new projects and smarter hires to repair it.

j / k navigate · click thread line to collapse

0 comments

mancerayder3mo ago

I'm with you on the avoiding tedium, on-call and monitoring and overall Operations pieces of it.

There's an infrastructure creation aspect where you're creating automation systems and passing it along for others to maintain. I personally think that's a sweet spot.

j / k navigate · click thread line to collapse