[artemisyna]

I don't get this question. Automation is the job.

We (mostly) don't code in assembly anymore because there are compilers. Your can say that writing high level code (merely "configuring things" in your parlance) is more "boring" than say, register hacks, but that's a bit shallow. (Also, something something leaky abstractions making the whole "it'll only be configuring things!" kind of a moot point.)

Consider programmers from the 80s/90s or early 00s. The ones that still have jobs today are the ones that have kept up with trends and adapted, or otherwise had the luck of being at a place that hasn't. It's the same for the future. Stagnate on old tech, have your career die on the old tech.

[minimalismhuh]

Good point!

So my strategy with the fundamentals are a dead end in other words. I would therefore rephrase your last sentence to:

"Stagnate on old methods, die on old methods."

My focus on fundamentals was really not productive. The people that I referred to as "naysayers" were right. I was wasting my time learning about fundamentals and stuff aka reinventing the wheel to understand why something works.

Hmmm... I need to reflect on my old perceptions and views now and error correct or rather "bugfix" my brain.

Thank you too! :)

Edit: to clarify what my goal was in all this: Basically, if you understand or rather know something deeply you have "power" (as knowledge will give you power). But again this way of thinking seems to be deeply flawed and employers don't appreciate it apparently.