Genuine question then.. how are we supposed to function properly as software engineers, especially in jobs with long feedback loops?
The nature of my job is that I'm almost more of a train conductor than a software engineer. I configure a job, run it, then wait for 10-30 minutes to get the results. I do this for maybe 5 jobs at a time, on 5 different projects. Naturally I feel a lot of stress and cognitive burden while doing this but I figured it's part of the job.
Is this normal for backend, distributed-computing heavy jobs? Is there a better strategy I can adopt? Should I try to get a new role with a shorter compile-test feedback loop?
The nature of my job is that I'm almost more of a train conductor than a software engineer. I configure a job, run it, then wait for 10-30 minutes to get the results. I do this for maybe 5 jobs at a time, on 5 different projects. Naturally I feel a lot of stress and cognitive burden while doing this but I figured it's part of the job.
Is this normal for backend, distributed-computing heavy jobs? Is there a better strategy I can adopt? Should I try to get a new role with a shorter compile-test feedback loop?