7 ms·
> Wary self-automators, he speculates, “don’t trust our workplaces. The boss is going to say thank you, good work, now do it again.” Well, no shit. That is wha
by cortesoft 8y ago
> Wary self-automators, he speculates, “don’t trust our workplaces. The boss is going to say thank you, good work, now do it again.”
Well, no shit. That is what the job of a programmer is - to keep automating things.
There are an INFINITE number of useful things we need to do as a society, so we shouldn't be upset if we automate one of them away. Move on to the next.
Of course, programmers should make sure they negotiate strongly to get compensated fairly for the work. I think it is a bit short sighted, however, to worry that you will end up like the guy who automated his job and was then fired and replaced by a lower skilled guy - who cares, you SHOULD move on at that point if the company doesn't want you to automate something else. There are plenty of companies that will hire you, and you can use the example of the previous company to show you can do it. This time, negotiate better compensation.
- crispyambulance 8y ago> Well, no shit. That is what the job of a programmer is - to keep automating things. I think that many of these scenarios are occurring when NON-programmers realize that their jobs are automate-able and they set out to automate them. It means picking up new skills, practicing them and putting them to use without the consent nor permission of management. It is not necessarily an easy path, it takes time, and there's going to be trial and error involved and although the discussion is about automating 100% of a job away, there's many other possible outcomes such as effort-multiplication, getting rid of the grunt work and gaining more time to focus on deeper problems. This is effectively "out-of-band" work that is a great experience for the individual but which _many_ organizations do not condone. A LOT of workplaces don't tolerate workers doing stuff that they're not being "told" to do.
- m000 8y agoWhat if you automated your job on your own free time?
- bradknowles 8y agoThen they get to pay you less because you work fewer hours to do the same job. Or they fire you because they don't need you anymore.
- 6nf 8y ago> Or they fire you because they don't need you anymore. This is the kind of ridiculous thinking I'm talking about in my other comment. You just made your job into a cheap, automated process. That's the most valuable thing you could do in a company! If you did that in my company, you'd get a promotion and you'd be put to work finding other things to automate. You're the kind of person every company wants! Why would we fire you? If we're dumb enough to fire someone like you, you're better off at another company anyway.
- bradknowles 8y agoIf companies were run in a logical manner, then your thought process would be reasonable. Sadly, while there may be some logical people in a company, many companies (most?) wind up not being run in a logical manner due to a wide variety of internal politics and societal issues. What you hope (and pray for) is that the logical people in a company are not also sociopaths, in which case you are really well and truly screwed.
- 6nf 8y agoThat's crazy, I don't understand how people are so negative about this. Sociopaths will NOT fire that person, they'd put that person to work automating other jobs. This is just how you run a business.
- crispyambulance 8y ago> Or they fire you because they don't need you anymore. I think people are just assuming that the typical case here is someone automating their job to a degree where they literally don't have to do anything. I suppose that happens sometimes if we are to believe anonymous reddit and stackexchange postings. What actually happens is that regular people who you would not assume are "programmers" start picking up computer skills and employ them in a piecemeal fashion a little bit at a time until eventually their day-to-day work becomes something quite different from when they started out. This has been going on for at least as long as there has been a computer on every desk. I think "software engineers" should not be so smug to think that everything worth doing is something that they're going to get a chance bid on and then get a project managers or scrum teams to implement. As for whether the person that does this gets fired or promoted depends on their skills at managing their peers and superiors, and what kind of environment they work in.
- imh 8y agoI'd bet many employees would be happy to work an hour or two per week. I'd be few employers would be happy to have employees work that little. It's not just a fear of being fired. It's a fear of the managerial mindset of "if they can do more each week, they aren't being challenged enough."
- cortesoft 8y agoThat is a larger societal question, though - how long should you be able to live off work you do? Is it fair for a worker to work for a few weeks, automating a job that used to be paid year after year, and then earn that money forever? Obviously there is a balance - a company shouldn't get ALL that savings (although in the long run, that savings would need to be passed on to customers, since competitors will also be able to automate the same tasks). At the same time, I don't think it is fair (or sustainable as a society), to expect to live forever off of work you did over a few weeks (no matter how valuable that work might be). If we allow people who automate things to live off the work of that automation FOREVER, then we are creating that sort of distopia that anti-technology people claim; that WOULD be taking jobs, because ALL of the benefit for the automation would be going to the automater and none to society. Society would still be paying the same amount for the resource, it would just all be going to the person who made it. Obviously, it shouldn't all go to a company either, but if ALL (or many) companies in the same field also automate, they will HAVE to pass on the savings to customers to compete. This will provide a net gain to society, since the resource is now cheaper for everyone (at the cost of the people who used to do the job). The cost decreasing with automation is REQUIRED to make it a net positive for society, and the automater taking all the rewards for the automation in perpetuity ruins that.
- tspike 8y agoTake the complexities of society out of the picture for a moment and reduce the scenario to a family unit living on subsistence farming with nobody else around: if the family is somehow able to automate their food, water, shelter and energy needs, are they entitled to live forever on that work?
- 8y ago
- s73v3r_ 8y ago" I think it is a bit short sighted, however, to worry that you will end up like the guy who automated his job and was then fired and replaced by a lower skilled guy - who cares, you SHOULD move on at that point if the company doesn't want you to automate something else" Yeah, but that person still has to feed and house their family. And in some areas there are "plenty of companies", but not in all.
- 6nf 8y agoI've told this story a few times and I always get surprisingly diverse reactions to it, especially on Reddit. Back in the late 90s I worked at a place that sold all kinds of automotive parts. Everything from nuts and spark plugs to turbochargers and large assemblies. The secret sauce of this company was a small team of people who worked through thick supplier (paper) catalogs and figured out which parts from different suppliers are in fact interchangable by comparing their specifications. This all went into the database for the sales team's use. Well one younger guy in this team worked out a way to largely automate his job using OCR and spreadsheets. Instead of taking 8 hours to work through his day's load, he would do it all in an hour or two. Then he'd slack off for the rest of the day. Soon the manager found out but the manager was not upset, instead the manager was disappointed. Why didn't this employee share this system with the others? Why did he think it was OK to slack off for 6 hours a day instead of doing 4 times as many catalogs? If this employee worked for me, I'd be putting him to work finding other things to automate! In the past I've had many comments from people saying 'oh he should have kept it a secret' or 'he is getting paid to do X and if he is more efficient then why cant he slack off' or even 'oh no this is a disaster now most of that team will be laid off'
- romwell 8y ago>Why didn't this employee share this system with the others? Because the consequences of him doing that are unclear. And since one potential (if not likely) consequence is management would simply retain 1/4 of staff doing this work and fire the rest, why would he share that? Was there a huge sign at his workplace outlining the consequences of automating anything? An explicit policy that would alleviate such (reasonable - read the article!) fears? I don't think so either. What was clear, presumably, is that as long as he processed X catalogs a day, he was getting his salary paid. That was what he was hired to do. And so that was exactly what he was doing. >Why did he think it was OK to slack off for 6 hours a day instead of doing 4 times as many catalogs? Because this is how work works. You pay someone to do something, and the expectations on the amount and kind of work - and the amount and kind of compensation - are discussed in advance. >If this employee worked for me, I'd be putting him to work finding other things to automate! Yes, and that's exactly the problem. What if there aren't any? What if there are, but he doesn't find them? What if he finds them, but doesn't know how to automate the task? He was hired to go trough books and compare specs, automating his employer's business was literally not his job. You see, your "reward" is not paying the employee 4X salary for being 4X efficient (you left that little part out!). Your reward is making the employee perform a more difficult job that they didn't sign up to do, presumably for the same salary (since you didn't mention paying them more). Do you still wonder why they kept their silence?