Certainly sounds like it. I find this bit pretty funny though:

> entire enterprise cloud stack written in only the newest of the new JS frameworks and containers

I'm of the opinion that the JS ecosystem is one of the few spaces where a healthy dose of NIH can save you a lot of time and money in the long run. And it seems like the only place where they didn't go for a custom solution.

At the end of the day, a lot of what NIH ends up being is employees extracting experience and resume value at the expense of business goals. It's kind of funny, then, that the JS ecosystem gives you a better resume if you have keyword soup with trendy frameworks.

Sometimes engineers are just curious about new and exciting stuff and don’t make the right risk/reward calculations.

Yeah it doesn't need to be a conscious and deliberate choice. If some folks have more of a tendency to do this and wind up with trendier resumes, then simply hiring trendy resumes for senior roles gets you there.

“But developer experience!”

Takes 3 weeks to debug.

That people are choosing js for drones boggles the mind.

They aren't. He said that was for their servers.

It makes a lot of sense for high level mission planning (more agile than other languages + it runs everywhere) and interacting with web apps.

What’s NIH? Not Inough Humility?

Not Invented Here https://en.wikipedia.org/wiki/Not_invented_here

Hah, "Not Inough Humility" seems to apply as well :)

That is so right. We’ll all be giving talks about this soon. NIH: Not invented here, aka not enough humility. :)

"Not In-House" is another common interpretation, in addition to "not invented here"; both mean the same.

I'm absolutely going to add "not inough humility" to the list from now on, it works just too well :)

more like too much easy money to burn