Coders Automating Their Own Job
You know how sometimes you love an article so much that you are annoyed you didn&#x27;t write it? This does a better job than I could have of tieing together a dozen threads of conversation that I&#x27;ve had with various friends for years.<p>I actually believe that there&#x27;s a culture war implied in this debate; the question of who deserves to reap the gains of automation is more than just philosophy or ethics. The question &quot;is there inherent nobility in work itself?&quot; seems to be just as much a political divide as any of the current popular hot-button issues. Your gut reaction says a lot about the regional values of where you grew up, whether you&#x27;d ever support a basic income, and whether you believe that someone&#x27;s refusal to work should condemn them to destitution.<p>The closest comparison is the attitude people have if they find a wallet. In Japan, you will get your wallet back with cash intact. Yet in the west, there exists a large contingent of people who believe with all of their heart that God wanted them to find it, that the person who lost it should have been more careful, that they are just having a lucky day. Unless God shows up and declares one side to be ethically correct, it will remain a toss-up.<p>One thing I find fascinating about the article is that it&#x27;s assumed the cleverness was the code written to automate. This is incorrect; the cleverness is in noticing when a task can be automated. Typically, the code itself is trivial.<p>Anyhow: automation is surely one of the best reasons every person should learn a little bit of programming. And even with that task accomplished, I suspect that the rate of people seeing the opportunity to automate will stay roughly flat.