2 ms·
There is something like a paradox of automation at play, too. Both business and programmers are aligned on not wanting drudgery, but this means that a) we under
by javajosh 3y ago
There is something like a paradox of automation at play, too. Both business and programmers are aligned on not wanting drudgery, but this means that a) we undervalue first-order work, and b) our automation reach often exceeds our grasp (k8s being an excellent example). Perhaps my thinking is colored by my recent read of Patrick O'Brian's excellent "Master and Commander" series of historical novels, about early 18th century English sailing ships, but the lack of automation is part of the romance - just to get from "here" to "there" required enormous effort. And who knows? Maybe if we take that approach we can press people into the software service by force, just like in the good old days!
- ElectricalUnion 3y ago> about early 18th century English sailing ships, but the lack of automation is part of the romance The highly hierarchical and structured command structure of a ship means that autonomous and intelligent human beings each make autonomous and intelligent decisions on the best course of action in a way that doesn't require constant and immediate upper layer attention all the time. The more limited amount of human beings required to upkeep a ship those days are mainly because of manpower shortage and cost reasons, not because the removed humans were "worse" at doing such operations. Those automation flows are in my opinion the same thing, they're replacing things because of manpower shortages or high costs of the previous thing, not because they're better.
- javajosh 3y agoCorrection: late 18th and early 19th century sailing ships.