Yeah. I have occasionally seen the opposite: worked a couple of places where leaders were so keen for people not to write code it became frustrating. But never had anyone breathing down my neck to spend more time writing code.
I will say this. After all the thinking and discussion is done, code is the means by which the desired value is realised, so if you're an engineer and you never write any at all there is a chance you might not be as involved in delivering that value as you might like to think. Plenty of situations where that's not true, of course, but it's definitely one of those things that can be a smell.
The only other difference mentioned is in implementation, but concepts are not defined by implementation. Obviously you could build a C compiler with neural nets. That wouldn't somehow magically turn everything into something completely different just because someone used a 'novel' approach inside of the black box.
Not too long ago there was a submission of a font-editor[1] and I gave it a shot trying things out, just to realize, that my creations looked off and ugly, not really understanding why. This helps a lot. So much nuance to so many things....
"Tiobe’s index is based on a formula that assesses language popularity by tallying the number of skilled engineers, courses, and third-party vendors pertinent to each language, based on results in search engines such as Google, Bing, and Yahoo."[1]
Never seen that happen. Do not know anyone who experienced this. Where and who are those managers?