|
|
|
|
|
by carlmr
2876 days ago
|
|
But basically the whole point of doing something in software is to automate things that are labor intensive. If you're avoiding things that save work you're not doing your job as a software engineer correctly. It's kind of like using an Ox in modern farming because you want more farmers to have work. You wouldn't do that because your farming business (barring some great marketing that lets you recoup the costs) would just go bankrupt quickly. |
|
I see where you're coming from but that's quite an oversimplification, don't you think? Software that drives a computer's graphic card, for example, which in turn gets used to run software that enables a physician to explore a 3D MRI, are just two examples of tasks that do not consist of automating manual labour.
(You could probably pay a lot of painters to paint a lot of pictures but hooking them up to the MRI might be a little difficult).
There's a lot of software that achieves new things, rather than old and well-known things really fast and without involving hands or a human brain.
I prefer to avoid discussing ethics on forums like HN, so I won't comment on whether or not working on software that puts people out of work is "the right thing to do" -- suffice to say that, if you wish to avoid doing that, there's plenty of room to do it while still doing your job as a software engineer.