I build and support new servers/racks to startups who throw money at new system hardware first, but no money to hire an IT to manage it. I’ve had too many awkward/frustrating interactions with software developers, data scientists, and even “CTO’s” (of their 5-20 person company) to suggest they hire someone more familiar with system hardware to locally configure and support their new systems if any issues arises- an IT person…
I’m sure you are one of the good ones, but I agree with OP that next wave of software developers (and data scientists) aren’t great with system hardware.
They are not great it because they have been raised on infrastructure that is composed of terrafom’d fargate + s3 + rds stacks. If they are a little more complex , logs get tossed into cloud watch, terraform interacts with route53 and ACM to get dns + certs.
At no point do they learn how/why stuff works the way it does, just that you can drop this chunk of teraform from chatgpt into your projects repo and now your using https.
I build and support new servers/racks to startups who throw money at new system hardware first, but no money to hire an IT to manage it. I’ve had too many awkward/frustrating interactions with software developers, data scientists, and even “CTO’s” (of their 5-20 person company) to suggest they hire someone more familiar with system hardware to locally configure and support their new systems if any issues arises- an IT person…
I’m sure you are one of the good ones, but I agree with OP that next wave of software developers (and data scientists) aren’t great with system hardware.
They are not great it because they have been raised on infrastructure that is composed of terrafom’d fargate + s3 + rds stacks. If they are a little more complex , logs get tossed into cloud watch, terraform interacts with route53 and ACM to get dns + certs.
At no point do they learn how/why stuff works the way it does, just that you can drop this chunk of teraform from chatgpt into your projects repo and now your using https.