It should be noted that programmers are not automating themselves out of programming jobs . They're automating themselves out of data entry, or testing, or any number of other mindless tasks easily done by computers.
We may not (yet) be able to automate ourselves out of programming jobs, but we can certainly leverage smart development practices into making the job a lot less labor-intensive. I'm experiencing a shift in that thinking right now. I write reusable, modular, tested code. My co-workers don't. I use a project management system (Phabricator, on my own personal server, which I maintain); the company doesn't. For most of t…
Coders Automating Their Own Job
21–30 of 499 posts
Re: Coders Automating Their Own Job
#22In Cybernetics there is a formal measure called Variety which is something like a limit or measure of complexity of a system. Programming can be considered the art of extracting the low-variety parts of a process into automation, leaving the high-variety parts to the (high-variety) humans. This process itself is low-variety. Therefore, from first principles, programming is automatable. Our programming environments will eventually look like automatic systems that we instruct with our intentions, and then they consult us as oracles to determine the high-variety parts of the necessary process, having automatically computed the low-variety parts.
In fact, this is already happening as fast as people can accept it. The limiting factor is not in the machines (they are already superbly fast) but in the psychology of the people involved. Most of the research and much of the technology already exists and is in many cases decades old. (Cf. "The Mother of All Demos" and Prolog.)
As time goes on, given the exponential nature of the meta-process, it will feel like a step function for many of us: one day relevant and employable, then the next day replaced by a machine and unemployable, and unable to learn the next thing fast enough to beat the masses of your peers competing against you in the same boat.
I realized all this years ago, and have been asking peers and coworkers, "If you could write a program that could replace yourself, would you?" However, to date, no one has taken the question seriously.
I find this article, appearing in a non-geek publication, to very heart-warming. Maybe people are finally catching on?
Anyhow, this is why e.g. Universal Basic Income is important: You're going to need it sooner rather than later.
Unless there is some essential economic activity that humans can perform that machines can't we are all on the "discard pile" of history.
I actually think we'll just mellow out and enter a Golden Age, but again, only as fast as we can accept it. Certainly the Universe is willing for us to live in peace and harmony, it's up to us to choose to, or not.
Re: Coders Automating Their Own Job
#23Re: Coders Automating Their Own Job
#24The employer is paying you for the product, not the effort. I see no moral quandary here, nor any compulsion to notify the employer. They're getting what they want, that should be the end of it. EDIT: And I would add, for anyone that has automated their job in this way...what you should really be doing is scaling it up, and finding other companies who are probably paying employees to do the same thing. Then start you…
Careful, if it gets out that you wrote the code to automate your job as a coder while actually at your job, your company most likely owns that IP.
Re: Coders Automating Their Own Job
#25It should be noted that programmers are not automating themselves out of programming jobs . They're automating themselves out of data entry, or testing, or any number of other mindless tasks easily done by computers.
They do that to and have always done so. It's barely remarkable because it is expected and part of the job. The problem is you can't benefit from that, as soon as you automate one part, you are given other tasks.
Re: Coders Automating Their Own Job
#26Re: Coders Automating Their Own Job
#27I learned that I was taken advantage of.
Re: Coders Automating Their Own Job
#28I realized at my last job that I was working to essentially replace myself and my co-workers. It was a pretty sobering thought. We often joke about training our replacements but we're definitely in an age where it's just as easy (if not easier) to build our replacements. This doesn't have to come in the form of AI which can ingest requirements and write code. It typically comes in the form of automating specific aspe…
You've just described the purpose of the entire software industry. Did it really not occur to you that writing systems to automate tasks would displace anyone doing those tasks manually?
Re: Coders Automating Their Own Job
#29Re: Coders Automating Their Own Job
#30Well, 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.