You're viewing a single thread.
I managed to complete Starfield during my work hours with no complaints. It's nice reaching the point in a job where you figure out how much you're actually expected to do.
What job?
Starfield QA Tester.
Isn't that just everyone who bought the game?
Do I still get the title if it keeps crashing before the ti
Dev/SysOps, because if you build shit that doesn't collapse then you can spend time experimenting with improvements instead of babysitting application clusters.
How is that? I've had at least one friend in the Dev space recommend DevOps to me because of the way I contextualize systems, but I'm worried the work requires technical expertise and I've stubbornly refused to learn any programming
Less programming, more file templates. I did more scripting as Desktop Support than I do as a DevOps engineer. Most of the automation is handled by existing software. The main job is figuring out how to install software in an environment, then making templates that can replicate the install with different parameters and minimal effort.
I came into it with a CS degree as a graduate but I learnt most of it on the job.