4 ms·
> A few years ago I made a vow to myself that I wouldn't work on software that puts people out of jobs. That implies you can't do anything to make people more
by JoshTriplett 10y ago
> A few years ago I made a vow to myself that I wouldn't work on software that puts people out of jobs.
That implies you can't do anything to make people more productive. If you produce software that makes people more productive, some companies will do more with the same people, but other companies will employ less people. Either way, though, you'll put some people out of jobs, and not all of those people will get the new jobs you create; even if you create more jobs than you destroy, you can't guarantee that everyone who had a job before will have one after. Improving productivity via some new tool has a similar effect to replacing low-skilled jobs with high-skilled jobs, just with a smaller scale and skill differential.
I don't think you can reasonably use "number of people put out of a job == 0" as a sole value metric, to the exclusion of all else. It's certainly worth including "number of people put out of a job" one of many factors you value, but not to the exclusion of all other values.
- mathgeek 10y agoAnother thought that comes to mind is that if you're not going to work on anything that "puts people out of jobs," it would seem hypocritical to use any tools that make your job easier. After all, if you're able to increase your own productivity, then we don't need as many developers. It's one of those thoughts that feels good, but really isn't practical.
- dllthomas 10y agoMaybe. Improving efficiency can sometimes increase consumption of a resource.
- JoshTriplett 10y agoExactly. Along the same lines, don't do anything to improve your interview process and find more productive people, because otherwise you could employ more less productive people, if you value "number of jobs" above all else.