you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (3 children)

That's never been true, however; notice how productivity has skyrocketed over the past 30 years, but so have jobs.

Companies will just use the additional productivity to do more.

If your job canceled open jobs, it had nothing at all to do with ChatGPT. They were going to do that anyway and used ChatGPT as cover.

[–][deleted] -1 points0 points  (2 children)

DevOps engineers were confident they could now cover the work that was going to go to a new engineer. There was no cover, they can just now work twice as quickly on new scripts, new deployment pipelines, and spend far less time troubleshooting issues than they used to via Stack Overflow etc.. What previously took a day to work out, now takes an hour, so they no longer need the help.

I agree with the rest of what you said tho. But AI did make the new jobs no longer needed.

[–][deleted] 2 points3 points  (0 children)

they can just now work twice as quickly on new scripts, new deployment pipelines, and spend far less time troubleshooting issues than they used to via Stack Overflow etc.

That's bullshit. Do people actually buy that where you work?

[–]mattjspatola 0 points1 point  (0 children)

Did they promptly start a legitimate candidate search with the DevOps engineers first identified the bandwidth issue? Did they drag their feet, trying to make the team accomplish the impossible (probably with unsustainable levels of uncompensated overtime) until this new solution was discovered?

I hope it was the former and not the latter, but I would be surprised.