[Osiris]

I find that take quite interesting considering the rapid pace at which software and computing changes over time. I would expect that by the time I retire in 30 years that nothing that I do right now will exist or be at all relevant.

I use certain software right now for programming that is completely different than what I used even two years ago. I work in completely different technology stacks and completely different tools.

Why would restrict myself to only using a set of tools that I KNOW will existing 20-30 years? What happens when some breakthrough technology comes that comes with it's own stack and toolset? Do you ignore it or adapt?

I actually enjoy switching between various technologies and tools. You get a different perspective, learn new things, get out of the rut and into a new challenge.

I really hope that in 3 years I'm not using the same tools I am using today.

[Crito]

Vi style editing has lasted entire careers already, and provided "programming" remains at it's core a matter of manipulating text files, I see no reason for it to not last mine. The day the industry transitions to "LabView 2: Electric Boogaloo" is the day I tap out of the industry.

> I actually enjoy switching between various [...] tools

I guess that's the difference between you and I. I don't, at all. I find satisfaction in what I do, not how I do it. Learning new tools for no reason other than I picked the wrong one to learn five years ago and the developers of my old tool packed up shop is something that I think is to be avoided at all costs.

And to be clear, I am more than willing to pick up knew technology that I believe will have significant staying power. Git is an example; whatever version control system that will replace it in 10-15 years will look significantly like it. Git's CLI interface is not an example; I know how to do what I need to do in Git, I know how Git works 'under the hood', and I know how to teach myself the rest on demand, but I do not spend time memorizing the intricacies of the various flags to the various git commands. That knowledge will likely become useless in 10 years or less.