Hacker Timesnew | past | comments | ask | show | jobs | submitlogin

This is my experience too, albeit sometimes it does feel good to have an infra specialist on the team. Edge cases do happen.


That’s what the AWS Business Support is for.

But at least three of the senior engineers (including me) I feel could hold our own against any “specialists”. My experience are too many of the “specialists” are old school netops people who got one certification and treat AWS like an overpriced colo.


AWS likes to pawn their customers off to Certified Partners for outsourced solutions.

I'm a software engineer who went the specialist route because it does take real skill to do this well. Yes, I am embedded on a team of old school netops people now, but I'm in charge of all of this and I get to drag them kicking and screaming in to the modern world.

Specialists are worth it if you find the right one.


I’m a software developer/architect/team lead/single responsible individual depending on how the wind blows, but after a few years of adding AWS to my toolbelt, I think I can hold my own and I have been recruited to be on the infrastructure side.

Old school netops folks are so afraid of becoming less relevant they do their best to keep control. But at least they are harmless compared to the ones that have tried to transition to the cloud. They are actively harmful costing clients and companies more with little to show for it.

And no I am not young. I’m 45 and started programming in assembly in the 80s.

“lift and shift” should be phase 1. Not the end goal.


I think we pretty much see eye to eye here :)




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: