I think that’s just IT jobs in general. I noped out after 15 years, no fucking clue what I’ll do but I can tell you it’ll be anything but IT
IT workers desperately need to unionize. There is so much bullshit that happens, folks are expected to do three different roles at once, have multiple technical stacks they are experts in, and work extra hours + be on call after hours or on weekends.
100%. A full on IT Workers Union would immediately become one of the most powerful weapons in fighting the oppression of the capitalist class. An IT strike could be effective enough that a general strike wouldn’t be necessary
That’s true. Let the largest BGP routers go down for 5 minutes and any demands the people who run them have would be met.
Wait what? I’m tryna enter this field because I heard it was chill
It can be. I often find it “bursty.” I’ve had months at a time when I had stand-ups and then “do whatever you want” for the rest of the day. I generally did do useful work, but there were plently of days when I was just chilling out.
Ive also had months where I ran from fire to fire while on fire, spreading even more fire. Also, there was fire.
It juat depends. If some org treats you as disposable, pays like shit and lights your hair on fire as you walk in, y’all should walk back out. The next org will probally treat you better, because there are good orgs out there. Even the good places get busy for a bit though. Just make sure that busy comes with money and that it ends at some point.
This is how I would describe my experience. Sometimes it’s crunch time and most of the time it’s fuck around time. After crunch time I always throw a tantrum about how if we only bothered with planning we could largely avoid it.
Just make sure that busy comes with money and that it ends at some point.
Excellent point.
I am so sorry.
It depends entirely on the company you work for. Even then, I wouldn’t exactly describe the work as “chill”
Cold sweats are chill
Is cloud engineer the name for devops this week?
I thought devops was a way to get a guy to do a whole team’s job by giving him a silly title.
Well Devops isn’t a role. It’s an approach in which bridges development and operations and integrating it in the team. It isn’t sticking a cloud engineer (cloud biased sysadmin) in the team. It’s about collaboration and delegating and supporting.
Cloud engineer is unfortunately what many orgs think devops is.
We call ours “cloud DevOps engineer”, heh.
Ah I see you read the book
Fancy title for the developer that gets yelled at when the CI pipeline is broken. Also a good chance they are the one that broke it.
What about the cloud engineer job do you dislike the most? I’ve been in the field for 7-8 years now and still find a lot of joy. Granted, the most frustrating parts of my job is lack of influence I have over the decisions that get made, but I moved to a team lead position to at least have a little say.
I hate everything about cloud engineer especially when tweaking & deploying, after that your boss blame you because the company got higher bill just because the apps have tons hidden micro service & peaked the server like crazy & your coworkers that made the apps got praise because your boss & project manager didn’t know anything about IT