Earlier quoted context omitted.
> I think the fundamental principles of software engineering haven't changed a whole lot since then. Not sure I agree with that. A lot of todays best practices and workflows (and the tech to go with it), especially considering team and release management, simply weren't around or at least widespread even twenty years ago. You know, stuff like CI, TDD, DVCS etc. etc.
> CI, TDD, DVCS Are any of these concepts particularly difficult to understand for a seasoned developer? I have a really hard time imagining that a C and SVN expert couldn't learn how to use git "well enough" in an afternoon, and effectively within a few days, for example. In particular, the freaking author of git is an 80's C programmer and SVN expert...
Depending on the personality of the developer: Absolutely. And most of the time it's not about the ability to understand, but the willingness to learn.
Yeah, it's a cliché, the old fart, set in their ways, "get off my lawn!1". I know, I'm guilty of it myself sometimes . :)
And it's one thing to learn some tech well enough to use it, and still another to grok the concepts and its ramifications, to actually get the whole picture of concepts, procedures and tools currently available to you, to be of help in higher-level planning and strategic decision-making. You know, all the stuff bosses are paid for. :)