Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As software developers we implement change which often mean others lose their job. I've worked myself out of more jobs than I care to remember, automating ruthlessly, fixing even when it meant I was redundant as a result. To not do so would make me guilty about all those systems I wrote which made others redundant. That's really what I.T. was for years ago. Was a time I was like some horrible spectre. If you saw me that meant yo' ass. Once I interviewed some users about some task they were meant to be rekeying, they hadn't done it for months as the old requirement had gone. I followed it back to the person who was sending the first part, a nice little old lady and told her gleefully she didn't need to do that onerous first collection task anymore, whereupon she informed me that it was literally all she did. I just left.


I think that's just about the right thing to do, the changing job market and availability of work is a governance issue, trying to tie technological progress to governance is like tying a brick to a unicorn, the results undesirable at best. One of my big pain points is unemployment, I was taught that the last thing a economic entity wants in a capitalist environment is a scarcity of labour that might drive up the cost of production, therefore my government, and many others, have in their remit a less than 100% employment strategy, the unemployment of X% is financially of benefit to GDP, it seems overly cruel that we punish the unemployed with a low salary, they are a crucial part of the machine that is supposed to care for all.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: