tro2102

Cool!

nit: you've got a casing mismatch between Devops and DevOps

I would also venture a guess that someone on hacker news who claims they know nothing about how an ipad or produce transport works isn't necessarily someone to pay close attention to.

Did you ignore "H1-B" on purpose?

I have both of these characteristics. Where did you learn it was a subtype of ADD?

Same here. Depending on the team I'm leading, I can actually consider not having the current stack a plus, as an outsider's perspective on architecture can help grow a team and codebase that's been stuck doing things the same way for a long time.

There's some penalty in ramp-up time, but I find it more than pays for itself down the road.

how about "suck it up and do it anyway"?

I don't necessarily disagree with this sentiment, but this doesn't really address the question, which is about what happens to an industry when it's made redundant by technology. Cab drivers competing with self-driving cars can't "suck it up".

"what if they don't want to" in regard to people working?

Again, I feel you haven't read the spirit of this comment accurately. What happens to an entire class of working people (truck drivers, for instance), when their trade is replaced by tech which is 1/10 (conservatively) the cost to produce? I too want to say innovation is worth it, but it's definitely worth the thought cycles to consider what happens when we make an entire workforce obsolete.

This is the first step to that solution, though - if all cars are self-driving optimally, that 2-4 hours rush becomes much shorter.