You know how sometimes you love an article so much that you are annoyed you didn't write it? This does a better job than I could have of tieing together a dozen threads of conversation that I've had with various friends for years. I actually believe that there'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 "is t…
One thing I find fascinating about the article is that it'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. I have told my work more than once that if they wanted to get the most out of me they should put me on the "front line" for a month or two, and let me decide what needs to be automated.…
Coders Automating Their Own Job
331–340 of 499 posts
Re: Coders Automating Their Own Job
#332Earlier quoted context omitted.
> 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. A large part of how America sees work, poverty and wealth was historically influenced by the Protestant Work Ethic, and I think that lingers quite a bit today. I think it's why a lot of people view the poor as…
I think this doesn't quite get it. Will "hard work" lead to success? No, not exactly. I don't think anyone believes that. A prisoner in a work camp works hard. Hard work combined with personal agency leads to success. Are you responsible for yourself? That is, are you taking responsibility for yourself? If so, you will find a way to make yourself successful. If you are looking for someone else to take responsibility…
Re: Coders Automating Their Own Job
#333Earlier quoted context omitted.
I would be sad that it seems they didn't feel they could trust me, but if they did the job well and for a good price why wouldn't I hire them again? Also, they're not my employee. I contracted them for a one time job. Totally different working relationship.
You say you would feel "sad". To be honest, I would feel cheated. And to set up this smokescreen with pseudo-gardening people (or prerecorded data entry screencaptures to stay with the article) is outright fraught, IMHO.
I value outputs.
To worry about how work is done if it is done well is micro-management.
Some people do want to pay money to have employees that look busy. I knew someone (in America it has to be said) who lived on a road where one person would constantly be getting gardening done just to show that they could afford it. It was constant re-work and pointless, which just showed off how much money they had. Maybe there is an element of that at work.
Security guards and secretaries are a similar phenomenon. They're not really needed, so god forbid they were to study for evening class while at work.
Re: Coders Automating Their Own Job
#334You know how sometimes you love an article so much that you are annoyed you didn't write it? This does a better job than I could have of tieing together a dozen threads of conversation that I've had with various friends for years. I actually believe that there'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 "is t…
Re: Coders Automating Their Own Job
#335It was a business critical application I inherited that was highly unreliable, my job was to keep it running. I just reworked the code so that it ran reliably and was resistant to outages etc. I also added in a few scheduled tasks etc to keep it ticking over
Re: Coders Automating Their Own Job
#336This article really highlights how odd our methods of valuing output are. Ultimately if someone is idling for 6 years because they've written a program to do their job for them, who cares? They are delivering the same output which hopefully the company deemed was valued at X amount BECAUSE it delivers Y amount of profit/returns. This article is actually touching on a deeper level of dysfunction in how we do things li…
> This article really highlights how odd our methods of valuing output are. Ultimately if someone is idling for 6 years because they've written a program to do their job for them, who cares? They are delivering the same output which hopefully the company deemed was valued at X amount BECAUSE it delivers Y amount of profit/returns. Their boss cares. This is capitalism, and capitalist ethics say you should be fired if…
Re: Coders Automating Their Own Job
#337You know how sometimes you love an article so much that you are annoyed you didn't write it? This does a better job than I could have of tieing together a dozen threads of conversation that I've had with various friends for years. I actually believe that there'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 "is t…
I once returned a wallet, cash, everything intact. Called the guy when I found it. He totally panicked. Was odd. When I handed it to him, that face! Worth it. Amazingly, he proceeded to try and give me the cash. Was an effort to decline. At the time, I really needed a warm fuzzy. The lost wallet was a great opportunity, and I got a good one. But, our conversation basically centered on, "who does that?" Indeed. The st…
Re: Coders Automating Their Own Job
#338Re: Coders Automating Their Own Job
#339Earlier quoted context omitted.
When most people or organisations are purchasing a service, they're usually mainly concerned about the value that service will bring them. The amount of effort required to produce that value, helps to dictate market conditions and the amount of competition; aside from this, ultimately I don't think effort matters so much when you consider it in terms of B2B transactions. Eventually, if a service is easy to supply—com…
It's because there's a conflict of interest in who reaps the benefits. If the company makes the decision to automate, it's clear that it's the company that reaps the benefits. If a worker chooses to automate, it's ambiguous.
Re: Coders Automating Their Own Job
#340A question for the people that have a positive attitude towards keeping time savings for yourself instead of passing them on to your employer. Would you be also okay with the following situation: You have someone remodell your garden. He comes up with an estimate of 1 week worth of full-time work for two people. Based on your experience this seems reasonable and you agree on a fixed price of 10000$. Two scenarios of…