• footfaults [none/use name]
    ·
    edit-2
    3 years ago

    I feel guilty for doing it, but I was promised a team of people that would help share the load, and I have cycled through like 4 contractors and 2 full time employees and two years later I'm still picking apart their pull requests because they keep making the same mistakes over and over.

    The contractors learn a little, then quit or leave, and I'm expected to just teach the replacement, over and over.

    I have job security, but I'm just continuing to automate more and more of the work and make it more complex and my co workers can't keep up, but we are able to deploy fleets of devices on faster and faster schedules and they just keep moving up the project schedules to match every timesaving automation I build.

    So now I meter out my productivity. Because if they keep moving the schedules up, eventually they'll move it below a certain threshold where issues in the physical deployment will cause timelines to slip and they'll go fucking nuclear, because apparently a date slip is far worse than it taking 6 fucking months to rack and stack and deploy something. What matters was that it matched the schedule they pull out of their asses at the start.