Ironies of Automation (1983) [pdf]
web.archive.org
Ironies of Automation (1983) [pdf]
1–10 of 40 posts
Re: Ironies of Automation (1983) [pdf]
#2Ironies of Automation - https://news.ycombinator.com/item?id=33476157 - Nov 2022 (5 comments)
Ironies of Automation (1983) [pdf] - https://news.ycombinator.com/item?id=23300195 - May 2020 (11 comments)
Ironies of Automation (1983) [pdf] - https://news.ycombinator.com/item?id=19132724 - Feb 2019 (27 comments)
Ironies of Automation (1983) - https://news.ycombinator.com/item?id=18230258 - Oct 2018 (3 comments)
Ironies of Automation (1983) - https://news.ycombinator.com/item?id=17587611 - July 2018 (1 comment)
Ironies of Automation (1983) [pdf] - https://news.ycombinator.com/item?id=9756838 - June 2015 (2 comments)
Ironies of Automation (1983) - https://news.ycombinator.com/item?id=7726496 - May 2014 (5 comments)
Re: Ironies of Automation (1983) [pdf]
#3Re: Ironies of Automation (1983) [pdf]
#4The endgame is that we will be spending 99% of our time restarting IDEs and clearing caches to get rid of nonsensical errors, but since we will be 1000x as productive in the remaining 1%, it will still be worth it economically.
Re: Ironies of Automation (1983) [pdf]
#5The endgame is that we will be spending 99% of our time restarting IDEs and clearing caches to get rid of nonsensical errors, but since we will be 1000x as productive in the remaining 1%, it will still be worth it economically.
And by productive you mean producing new problems that need solving instead of really solving anything, so that business can continue to make money?
Re: Ironies of Automation (1983) [pdf]
#6Re: Ironies of Automation (1983) [pdf]
#7Re: Ironies of Automation (1983) [pdf]
#8The endgame is that we will be spending 99% of our time restarting IDEs and clearing caches to get rid of nonsensical errors, but since we will be 1000x as productive in the remaining 1%, it will still be worth it economically.
Funny, I remember the discussion of this paper at my university a few decades ago. On your topic, I remember also a case that was discussed on a disinvestment of a fully automated factory. Loads of money was invested in the automation, but on several spots it still needed humans to glue the processes together. This work was so limited and dumb that no workers could be found who were able and willing to perform this t…
I estimate the thing crashed from 2-3 times per day to every 3 days or so with the later more often. Took about 15-20 minutes to clean up with 15. Say 1 person would need 4-5 hours. Then they gained 4.5 hours of production per incident (with 15 people)
15 * 8 hours * 3 days = 360 hours
each of the 4.5 hours would then cost 80 man hours.
Better numbers with more frequent crashes.
Investors didn't like to see people sit, chat and drink coffee most of the day.
The solution was to remove some machinery and all of the chairs. People had to work with insane speed to keep up. No time to scratch your itch, the work spot was designed for a machine, the one in storage.
Imagine working there and going from drinking koffie all day to insane speed conveyor belt work because someone put the machine in storage because an investor might visit 1 time per year.
Really brings out the best in people (ehm!)
Re: Ironies of Automation (1983) [pdf]
#9Related: Ironies of Automation - https://news.ycombinator.com/item?id=33476157 - Nov 2022 (5 comments) Ironies of Automation (1983) [pdf] - https://news.ycombinator.com/item?id=23300195 - May 2020 (11 comments) Ironies of Automation (1983) [pdf] - https://news.ycombinator.com/item?id=19132724 - Feb 2019 (27 comments) Ironies of Automation (1983) - https://news.ycombinator.com/item?id=18230258 - Oct 2018 (3 comments)…