> Ahh government work. Can always tell because y’all do
Uhh I work in the Professional Services department of a little cloud provider based out of Seattle you might have heard of…
Sure I’ll work on a project porting to EKS (managed Kubernetes) if they are already familiar with it. But rarely will I suggest introducing the complexity of it unnecessarily.
I’ve worked with governments, colleges, F500s, startups, and everything in between.
I mostly focus on green field app dev. But I know my way around “DevOps” [sic]
Ahh government work! Look I’m just poking fun at the fact that people who call them COTS are either government or sell to government, it’s not a pejorative.
Not doubting your expertise at all, I’ve worked at shops that are entirely vm based, I just think that when it comes to
making dev teams happy in an on-prem world giving them a k8s cluster has so far never not been a good decision. I can hide so many of the ugly realities of running a production service.
You have to talk the talk to show them that you’re one of them. I can go from a decent midwestern neutral accent to my natural southern drawl depending on which state I’m working with too :)
And besides, even when I worked in the real world as your bog standard Senior enterprise dev, I got to the point where I wouldn’t work at any company that had on prem architecture.
My main reason for going to the cloud was not that I didn’t want to deal with administering servers, I didn’t want to deal with server administrators.
Uhh I work in the Professional Services department of a little cloud provider based out of Seattle you might have heard of…
Sure I’ll work on a project porting to EKS (managed Kubernetes) if they are already familiar with it. But rarely will I suggest introducing the complexity of it unnecessarily.
I’ve worked with governments, colleges, F500s, startups, and everything in between.
I mostly focus on green field app dev. But I know my way around “DevOps” [sic]