>Is destroying jobs an appropriate driving force for a young company? I think the answer is no.
I think the answer is yes. Making human effort unnecessary is a good measure of value having been added to the world, because that human effort is now free to do something else.
Pity the stagecoach drivers, but don't let it stop you from celebrating the automobiles.
Really? There are a lot of jobs that could be automated. If you are writing software with the goal of improving current processes, sometimes you can get a better result by looking at WHY the process exists, and if it could be replaced entirely.
An example: Self driving cars will eventually put Taxi Drivers out of jobs. Does that mean a Start-up that wants to be in this industry is evil? I don't think so.
Hi everyone I'm the author of this post.
The point I'm trying to make is that there is a difference between your mission and the mission's unintended outcome.
As an engineer, I don't believe my mission is to put people out of jobs. In response to some of your points:
Yes, self-driving cars will put people out of jobs. But is that the mission of Google? No, their mission is to make people's lives easier / better.
Yes, electric cars will put gas-pump attendants out of jobs. Is that the mission of Tesla? No, their mission is to make people's lives better through sustainable transport and removing our dependence on fossil fuels.
I think it's important to focus on the value-add portion of what we do, and especially not treat the negative fallout (people losing their jobs) as some kind of marketing angle.
Distasteful? Maybe. Ineffective? Quite probably (considering the decision makers who are buying a Social Media tool are often Social Media Managers). However, if you're going to be as uncomfortable with software eliminating certain job categories and putting people out of work as the OP claims they are, you probably shouldn't be working in technology.
Salesforce (a company specifically mentioned by OP) certainly didn't aim to put salespeople out of business. It did, however, greatly reduce the need for assistants and secretaries that used to be instrumental in keeping salespeople organized, thus eliminating many such positions. Mailchimp (another company mentioned) certainly created some new email marketing positions, but in the process it helped optimize email-use, which is itself a kind of optimization of traditional mail. Thus one could reasonably argue that Mail Chimp helps put people in the paper industry and in the Postal industry out of work.
Adding/creating value and the destruction of jobs are not mutually exclusive. Value can be created through innovation that results in job destruction. Furthermore, a product or service that eliminates one job can easily be responsible for creating one or more new jobs.
The author's Salesforce example is particularly naive. While it would probably be inaccurate to claim that Salesforce alone slayed Siebel[1], the reality is that Salesforce did upend the CRM market. In doing so, Salesforce created significant value, but at the expense of established CRM software providers and many of the integrators that relied on the demand for their products.
[1] http://fortune.com/2014/01/23/lessons-from-the-death-of-a-te...
What about something like self-driving vehicles? In particular, Semi Trucks. That's a technology I look forward to, but it will destroy jobs. Self driving trucks don't enhance the ability of the driver, it replaces the driver. Self driving trucks can do 36 hours of driving in 36 hours. A human driver will take 3 days. Your whole truck fleet is idle at night, and you need huge cabs to accommodate basic living needs of humans. Etc.
I honestly hope someone is trying to make this happen, even though it'll completely kill millions of jobs. Hopefully the drivers can find new skills. The economy certainly wouldn't mind an extra 1 million programmers.
Destroying jobs with technology is one of the primary ways we've improved productivity over the past half century. I understand not everyone thinks that's a net positive, but if you're one of those people then you shouldn't try to create productivity software.
At the macro unless your name is Oracle your productivity software will reduce the number of people needed to accomplish a task. Assuming your software works of course. Patio11's main product is to replace secretaries, while improving customer retention.
Sorry, but there's truth in patio11's statement that, as a developer, "You’re in the business of unemploying people. If you think that is unfair, go back to school and study something that doesn’t matter." [1]
Doing things that matter, changing people's lives, that SHOULD change what jobs people do.
[1] http://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pro...