That’a the low value they’re talking about. And all of that stuff is accidental complexity.
To use their example, you need to know that dropping duplicates is a good idea (and why). Knowing what the syntax and api calls to do that is, in my opinion, unnecessary.
Even your example has unintentional complexity. A 'duplicate'? What's that? Do we compare the memory it points to? Through use of a custom comparator function?by an id or tag? APIs and entire languages are designed around how we define such seemingly simple terms.
Ultimately a language, be it a programming language or human one, is about communication. I find there to be value in knowing how to communicate effectively, even if employers increasingly disregard the value of such knowledge. Without it, we'll quickly find out why it's fundamentall quickly.
This is the same thing as pressing the power button on my computer; I want the thing turned on, I don’t want to have to know about memory training.
And then we wonder why apps are getting so much slower and bloated. That's fine if you don't want to think that low level, but someone needs to worry about performance. And others will need different needs for defining a duplicate in their different use cases.
The people who need to most think about performance are those making the frameworks and languages. Why are bloated electron apps so easy to make but building native cross-platform apps with similar ergonomics hard? Why are people choosing electron?
Yes. I am not a web dev, but I tend to fall into that category in my domain.
>Why are bloated electron apps so easy to make but building native cross-platform apps with similar ergonomics hard?
If you want to be blunt, it's political. Each OS wants to ultimately build its own moat, so there's less incentive to come together and make a standardized solution. Then Linux is a less centralized OS that makes theoretical cross platform support even harder. Cross platform applications get made despite that friction to fill the obvious demand.
The why's of which cross platform framework wins is hard to say. It only becomes obvious that whoever breaks out tends to win more, and it gets a massive flood of support, funding, and clients. So it snowballs up. Those who don't simply struggle to stay relevant.
Electron likely wins in the market aspect that bloat isn't enough friction to turn off a modern consumer with a modernish (10 years or younger) desktop. And it especially doesn't matter to phones (which tend to skew newer).
I don’t have to remember assembly intrinsic since the compiler deals with that, I just describe the higher level goal and it implements it.
It's a real shame a leader of an education company doesn't value the actual learning process. Those "low value" processes are the building blocks to understand and master high level concepts. I'm not spending my day to day thinking about the low level memory allocation in my job, but that knowledge and work helps immensely in how I approach the higher level assignments and wider architecture. And I still kick myself because my assembly knowledge is is only 1.5 semester's worth.
And yes, I still look up how to construct an array in C++. Not really because my memory is bad (okay, kind of), but more for the practice of reviewing API's and parameters and maybe making new revelations. I probably knew internally some 12 years ago I could set an initial capacity in one of the array's constructors. I didn't really "understand" the value in that until one random work day 4 years later as I was working through some in-house container packages.
You can even say that doesn't matter if you know what resize() is, but it's those little bits of learning nuggets that builds you up from a "fine engineer" to a "great engineer". Less the knowledge and more the work ethics built to obtain it.