> I find the wording of your last paragraph a little insulting.
And calling modern app development's probelms " due to arbitrary complexity and they are short term" isn't?
I do think that much of the aerospace technology industry uses dated methods. Same with much of the embedded field. There are certainly places that, for example apply modern best practices to embedded work, but most of those places are the exact same things that you're writing off: Google, Facebook, etc. Have embedded projects that follow best practices.
Focusing on aerospace specifically, I know of plenty of people who work in aerospace and don't use version control. That's plainly unacceptable. And I'd argue that the problems encountered there are much more self-imposed than at a Facebook.
Db engines again depend. There's a number of really cool modern relational database work, but the places where it happens (postgres, Google, cockroach labs) aren't places where someone who isn't interested in self growth are going to succeed.
The tl;dr here is that the impression I get from your comment is that you're describing a developer who let their skills stagnate because they learning things one way and don't want to keep up with changing processes. The fields you mentioned are fields that have such a stigma attached to them, and not unjustly. It doesn't apply to every person or project in those fields, but the people it doesn't apply to would succeed anywhere anyway.
And calling modern app development's probelms " due to arbitrary complexity and they are short term" isn't?
I do think that much of the aerospace technology industry uses dated methods. Same with much of the embedded field. There are certainly places that, for example apply modern best practices to embedded work, but most of those places are the exact same things that you're writing off: Google, Facebook, etc. Have embedded projects that follow best practices.
Focusing on aerospace specifically, I know of plenty of people who work in aerospace and don't use version control. That's plainly unacceptable. And I'd argue that the problems encountered there are much more self-imposed than at a Facebook.
Db engines again depend. There's a number of really cool modern relational database work, but the places where it happens (postgres, Google, cockroach labs) aren't places where someone who isn't interested in self growth are going to succeed.
The tl;dr here is that the impression I get from your comment is that you're describing a developer who let their skills stagnate because they learning things one way and don't want to keep up with changing processes. The fields you mentioned are fields that have such a stigma attached to them, and not unjustly. It doesn't apply to every person or project in those fields, but the people it doesn't apply to would succeed anywhere anyway.