Ive done all of those things in my current job, and they are unrelated to my actual job description. None of them are particularly hard. Heck, I’ve installed servers, welded mounting brackets, soldered components, run cabling, designed letterheads, built and maintained VM production servers in AWS, written software, visited clients, delivered goods, done sound design, edited video, written company policy, managed DNS records, and kept all the office plants watered and healthy. Im a technical writer. Some jobs just do be like that.
Sounds like you worked for some fucking stupid companies. Do what you’re hired to do, not be an entire IT department, custodian staff and administration. You are the only one losing in that situation.
Also what sort of company would give access to managing DNS and deploying ec2 instances to someone not in an operations role. Easiest way to run up your bills by introducing misconfigurations which can cost a lot if not rectified quickly.
I’ve seen load balancer routing traffic across AZs unnecessarily where a single checkbox was not clicked, costing $500/month until it was discovered. Also devs who think they need a cluster of c5.2xlarge instances for a simple webapp, where most of the requests were serving javascript files, and needed to be moved to s3/cloudfront.
Or maybe he’s worked for some small companies where none of those is a full time job and hiring 27 people to sit around for 97% of their time is not likely to be considered a terribly good business decision.
Ive done all of those things in my current job, and they are unrelated to my actual job description. None of them are particularly hard. Heck, I’ve installed servers, welded mounting brackets, soldered components, run cabling, designed letterheads, built and maintained VM production servers in AWS, written software, visited clients, delivered goods, done sound design, edited video, written company policy, managed DNS records, and kept all the office plants watered and healthy. Im a technical writer. Some jobs just do be like that.
Sounds like you worked for some fucking stupid companies. Do what you’re hired to do, not be an entire IT department, custodian staff and administration. You are the only one losing in that situation.
They pay me heaps, my job is interesting, I get to learn tons of new skills on their dime, and I average about 4 hours of actual work a day.
Also what sort of company would give access to managing DNS and deploying ec2 instances to someone not in an operations role. Easiest way to run up your bills by introducing misconfigurations which can cost a lot if not rectified quickly.
I’ve seen load balancer routing traffic across AZs unnecessarily where a single checkbox was not clicked, costing $500/month until it was discovered. Also devs who think they need a cluster of c5.2xlarge instances for a simple webapp, where most of the requests were serving javascript files, and needed to be moved to s3/cloudfront.
Well, I’m not incompetent at my job like that so its not really a problem.
The company is only 12 people, not a multinational.
Or maybe he’s worked for some small companies where none of those is a full time job and hiring 27 people to sit around for 97% of their time is not likely to be considered a terribly good business decision.
I have also been the IT guy in a tiny company