News for hackers. Stuff that matters.
Re:Intel's make-or-break 18A process node debuts for data ce... by LunaSea on Tuesday March 03, 2026 @04:10PM (#47239046)
> The company did need the same exact people to manage AWS anyway.

That is incorrect. On AWS you need a couple DevOps that will Tring together the already existing services.

With on premise, you need someone that will install racks, change disks, setup high availability block storage or object storage, etc. Those are not DevOps people.

Re:Intel's make-or-break 18A process node debuts for data ce... by mgaunard on Tuesday March 03, 2026 @04:20PM (#47239188)
Ops people are typically more useful given you probably already have devs.
Re:Intel's make-or-break 18A process node debuts for data ce... by ozgrakkurt on Tuesday March 03, 2026 @04:27PM (#47239285)
To be clear, I'm not writing about on-premise. I mean difference between managed cloud and renting dedicated servers
Re:Intel's make-or-break 18A process node debuts for data ce... by Dylan16807 on Tuesday March 03, 2026 @04:41PM (#47239454)
Even if you do include physical server setup and maintenance, one or two days per month is probably enough enough for a couple hundred rack units.
Re:Intel's make-or-break 18A process node debuts for data ce... by LunaSea on Wednesday March 04, 2026 @03:53AM (#47244830)
Ah sorry, yes, that makes sense.
Re:Intel's make-or-break 18A process node debuts for data ce... by lightedman on Tuesday March 03, 2026 @04:30PM (#47239320)
"Those are not DevOps people."

Real Devops people are competent from physical layer to software layer.

Signed,

Aerospace Devop

Re:Intel's make-or-break 18A process node debuts for data ce... by b40d-48b2-979e on Tuesday March 03, 2026 @09:02PM (#47242049)
What a naïve take. Real™ DevOps know what they need to know.
Re:Intel's make-or-break 18A process node debuts for data ce... by LunaSea on Wednesday March 04, 2026 @03:52AM (#47244828)
> Real Devops people are competent from physical layer to software layer.

This is usually not the case because DevOps are often people that mostly worked on cloud services and Kubernetes clusters and not real hardware since most companies do not have on premise hardware anymore.

Re:Intel's make-or-break 18A process node debuts for data ce... by ragall on Wednesday March 04, 2026 @11:29AM (#47249915)
There are no "Devops people". DevOps was created to mean a world where the DEVelopers are doing OPS, hence there cannot be "Devops people", as it would be a contradiction in terms. If you're specialized, you're just "Ops".
Re:Intel's make-or-break 18A process node debuts for data ce... by ocdtrekkie on Tuesday March 03, 2026 @05:05PM (#47239725)
People will install racks and swap drives for significantly less money than DevOps, lol. People who can build LEGO sets are cheaper than software developers.
Re:Intel's make-or-break 18A process node debuts for data ce... by PunchyHamster on Tuesday March 03, 2026 @06:33PM (#47240686)
> With on premise, you need someone that will install racks, change disks, setup high availability block storage or object storage, etc. Those are not DevOps people.

we have 7 racks and 3 people. The things you mentioned aren't even 5% of the workload.

There are things you figure out once, bake into automation, and just use.

You install server once and remove it after 5-10 years, depending on how you want to depreciate it. Drives die rarely enough it's like once every 2 months event at our size

The biggest expense is setting up automation (if I was re-doing our core infrastructure from scratch I'd probably need good 2 months of grind) but after that it's free sailing. Biggest disadvantage is "we need a bunch of compute, now", but depending on business that might never be a problem, and you have enough savings to overbuild a little and still be ahead. Or just get the temporary compute off cloud.

Re:Intel's make-or-break 18A process node debuts for data ce... by vel0city on Tuesday March 03, 2026 @10:33PM (#47242706)
> Biggest disadvantage is "we need a bunch of compute, now"

And depending on the problem set in question, one can also potentially leverage "the cloud" for the big bursty compute needs and have the cheap colo for the day to day stuff.

For instance, in a past life the team I worked on needed to run some big ML jobs while having most things on extremely cheap colo infra. Extract the datasets, upload the extracted and well-formatted data to $cloud_provider, have VPN connectivity for the small amount of other database traffic, and we can burst to have whatever compute needed to get the computations done really quick. Copy the results artifact back down, deploy to cheap boxes back at the datacenter to host for clients stupid-cheap.

Re:Intel's make-or-break 18A process node debuts for data ce... by rcxdude on Tuesday March 03, 2026 @07:48PM (#47241469)
Moving around the physical hardware is a truly tiny part of the actual job, it's really not relevant. (especially nowadays, see the top level comment about how you can do an insane amount (probably more than the median cloud deployment) with a fraction of a rack).