Hacker News new | past | comments | ask | show | jobs | submit
And a horse breeder was important to transportation until the 1920s, but it doesn't mean their job was transportation.

They didn't magically become great truck drivers.

Programmers do not deliver products, they deliver code to make products.

If the code is no longer needed, nor is the job. A different job will replace it with different skills required.

> And a horse breeder was important to transportation until the 1920s, but it doesn't mean their job was transportation. They didn't magically become great truck drivers.

Again: unrelated and pointless analogy. The horse breeder would be analogous to chipmakers or companies that make computers. Turns out they have more of a job than ever. They don’t need to “become truck drivers.”

> Programmers do not deliver products, they deliver code to make products.

That’s not even a little bit true. Programmers deliver product every day: see every single startup on the planet, and most companies.

Moreover, you said programmer. I didn’t.

I said software engineer/architect, as that was what the parent comment asked.

I chose my words intentionally. I am referring to people who engage in the act of engineering or architecting software, which is definitely not limited to writing code.

Yes, a pure programmer (aka a researcher or a junior programmer) may not fare as well, for the reasons you mentioned.

But that was never who we were discussing.

If you still think the code is the point, I’m not sure we’re going to see eye to eye, and I’m going to just agree to disagree. And if that’s the case, then you’re right: you may be left behind, keyboard in hand.