My wife says programmers just press buttons and look at a glowing rectangle all day. I think you've just done the equivalent.

Having worked both in software development and at a warehouse, I can vouch that both have multiple dimensions.

Oddly enough, both jobs involve sorting algorithms, and both can be completely derailed by poor management.

Let me work in a warehouse. What do you think how long does my initial training will take to be a picker at an amazon warehouse?

I will tell you: between 2 days and 6 weeks.

"shrinking its warehouse training time from a conventional six weeks to as little as two days."

How long do you think i have to train your wife to setup a kubernetes cluster, make sure it is secure, backuped and works efficient? Then when she knows that, how to build images, and write code in java, go, bash, ansible etc.?

If the answer is longer than 6 weeks, you see the difference. And don't get me wrong, i have seen people who had a 3 year education and start as juniors and miss a lot for years until they get it all right.

Yeah but a metric is a metric is a metric. That there are more metrics in one area than another is arbitrary.

You could just as easily say: all right LOC is the only thing that matters, we're not paying you to be right, we're paying you to write code so do it. And the warehouse could have thousands of metrics to measure the intricacies of working in a warehouse. Following that your argument easily applies to programmers as well. They deserve to be treated like crap.

That you view working in a warehouse as so simple,and that you talk about "deserving" so much reveals a lot. You're using metrics as an abstraction to hide behind so you can really say they "deserve" to be treated this way because they work in a warehouse.

But, really, whether someone deserves some treatment or not because of the job they work should be irrelevant.

Forget the LOC example. Let's just say failing tests. Pick any single thing you think is critical to software development. Regardless of what it is, would it be acceptable to you to have an automated process simply fire someone for not hitting this metric?

I feel like at some point we have to draw the line. We're going to have to coexist with automation and eventually it will get to software development, too. Some parameters about what we consider to be reasonable and unreasonable to automate make a lot of sense to me.

I also feel like we get very classist as software developers and fall into the I-am-special trap frequently.

We have drawn the line. Right now it’s at Amazon warehouse workers.

Also there is a critical thing to software development: Working for a business that makes money. If you don’t hit that metric, you’ll eventually be out of a job.

Plus, there are many more people who can pick up boxes than there are who can program.

We haven't draw any line at all, it's simply where it's been pushed so far.

I have drawn a personal line a long time ago. I do not use amazon at all. No PayPal, Hollywood, local restaurants without union contract for the employees and so on. The union have a search app to keep tab on what restaurants are ok. (Sweden only though). We don't have much laws for companies, the unions have to agree with the company organisations for a lot of the rules.

How does that differ from any other situation? Something is acceptable until it isn't...

That's what I'm saying. We haven't drawn any line here, we're just acquiescing at every step.

Then nobody ever draws a line. We just acquiesce at every step.