Consequential Efficiency

I had odd side tasks at a few previous jobs that while I couldn't automate them per se, I created some combination of spreadsheets and parameter-driven drawings/models that greatly reduced the time and all but eliminated errors.

The first time I did something like that, I was young and dumb and showed my boss and their management team. As a reward, I was given a ton more work and expected to do it all in less time, even though what I'd created was only applicable to about 10% of it. Then when I couldn't meet that workload, I was berated and had my "helper" spreadsheet and drawing made fun of in a meeting.

After that I made a similar sheet to help on a different task and only told a coworker friend...who then proceeded to tell management about it and take credit for making it. Karma being a bitch, though, he was just given more work to make up for that efficiency as well, and a few months later some of the variables changed and he was totally unable to fix the built in formulae to account for it, so it was basically useless to him, but he still had the work.

After that I just never told a soul about anything like that until maybe if I was leaving the job.

At my very last job before my current one, I had developed a 3D model that accepted a string of about 30 parameters and, as long as there were no conflicts, spit out a model that was 95% of the way to complete for maybe 60% of my normal workload, and as long as it was successful, it came with an associated drawing template that also auto-populated most of my work there...so basically taking a little bit over half my normal work and making it at least 75% faster. A game changer.

I sat on that shit for the last 9 months I worked there, using it, improving it, adding features on my own time, troubleshooting issues, etc. Said nothing to my boss or my one other coworker until literally the day I gave my notice. I figured it'd help my coworker handle the increased workload until they hired my replacement (but didn't want that asshole to get credit for my work) so I showed both him and my boss at the same time.

At first, both acted unimpressed and uninterested. After a few days though, my coworker was using it and quickly they realized the value. Instead of thanking me and asking how it worked and could be improved, they just told me "Use the time you have left to improve this to work on every possible variant of the type of part it works on, and also develop an equivalent for the (totally different) type of part your coworker makes. Have it done before your last day."

I had like 4 days left.

So I literally just said, "No, not going to do that. It took me months to get this one where it is, and it's stable and works on most cases. Trying to add that much to it in 4 days might break it. There's just not enough time, so no, I'm going to finish my backlog of work and clean up my desk area for the next few days and that will be it."

Yup. yup, you should enjoy your free time. And send the email right before the deadline

Words to live by

Seriously this.

Been in the industry for going on 15 years. Never happened the way this comic makes it out to be.

There is always work to be done. That employee ends up being a tech lead or IC and promoted.

Companies don't fire a whole team. They'll find ways to maximize that solution that automates a lot of work. Oh, you can automate a DB? Can you automate more things or train others to do the same?

And the whole team gets better and more creative work. I've watched my team evolve over and over. Ive jumped to a bunch of companies and continue seeing it happen.

It's hard enough getting good devs, so unless you work at a shit company, many hire real slow and often don't fire devs unless they're real bad apples.

And finally - Who the fuck wants to spend 8 hours making SQL queries manually? If your 40 hour job can be automated with a script, you're going to be unemployable regardless.

There are no good bosses.

The system is shit.

If they really needed to get around to doing that, the boss would've already hired another employee to do that task.

Not doing so implies that paying someone just for that task wouldn't be worth it.

That does not change when a worker becomes available from somewhere else.

Also, make sure you have to do something essential that no one else knows how to do to make the automation work so you don't risk getting fired or if they fire you they don't profit from the tools you created.

There was a user on Tales from tech support that had tons of great stories including one where he left with all the documentation for the tools he had created over years of work for a company and they were left with useless tools once he was gone!

I did a co-op position at the federal government during my undergrad where I automated my main task. I told my boss and he said that the efficiency was too high; they couldn't maintain the script when I left. He asked me to only report results in the usual timeframe (4 hours instead of 45 minutes) and to maybe download some Netflix.

the ideal boss thinks your job is way harder than it is

Always under promise.

In the US this is called constructive dismissal. It's a tactic used by employers to get away with firing someone but not getting hit by unemployment insurance payments.

The good news for workers is, it still counts as being fired and you still qualify for unemployment if you "quit" under these conditions.

This is what most places I've been at did even when I was the newbie in the OP

"Oh, you helped us with some basic IT knowledge and can do even more for us later if we keep you and don't treat you like shit? How about I get 6in or less from your face and scream so loudly that your ears ring a little when I'm done?"

For the person now jobless, sure.

Imagine? This is real life.

I think all the stuff that gets to the "front page" of lemmy from this community is actually all correct but idk why anyones first reaction to this would be antiwork. You still want people to work because ai cant program well enough today. I dont really understand the antiwork movement right now, maybe in 20 years.