News for hackers. Stuff that matters.
Re:We don’t use Kubernetes by toomuchtodo on Tuesday July 20, 2021 @10:15AM (#27893980)
You want your skills to be transferrable (unsolicited career advice). Someone isn't going to work on your bespoke infra management system for below or at market rate when those skills won't transfer to another org (and they'll be behind the curve compared to others who have been "in the trenches" with k8s during the same window of time). Google, Facebook, and similar get a pass because they will shower you in money for their bespoke infra work (and it looks good on your CV to other orgs, typically).

Personally, you don't have to be hip, but I want to be able to have another job in hand based on the tech I was working with and the work I was working on in a matter of days when I decide to bounce (or the decision is made for me). This is just good risk and career management.

(disclosure: infra roles previously)

Re:We don’t use Kubernetes by Sevii on Tuesday July 20, 2021 @11:33AM (#27895000)
There is also the quality of work factor. What is easier to use a bespoke infra or kubernetes? For the same pay I'd rather work with k8s than deal with whatever gremlins are buried in 'custom' infra.
Re:We don’t use Kubernetes by shadowgovt on Tuesday July 20, 2021 @11:35AM (#27895023)
> Google, Facebook, and similar get a pass because they will shower you in money for their bespoke infra work (and it looks good on your CV to other orgs, typically).

You left out "Their bespoke infra work tends to be the genesis of the commodity infrastructure other people are using."

It's not hard for a Googler familiar with Borg to pick up Kubernetes. It's not hard for a Facebooker with some UI work under their belt to figure out React.