Reminds me of when we were admonished to use a "real" compiled language rather than an interpreted, GC'd one, lest we lose our ability to reason about the system, cache, and memory.
Which reminds me of when we were admonished to continue using assembly, lest our "real" skills atrophy from too much cushy C development.
Which reminds me of when we were admonished to keep our scope and probe skills sharp, and read and understand the schematics of whatever computer we were on, lest we forget how to diagnose faults in its components.
Which reminds me of when we were admonished to practice calculating in our heads and keeping slide rule skills sharp, lest they atrophy to a calculator.
You don't need to "keep practicing" in order to maintain your understanding.
The best engineers know how our systems work down to more levels, but for average developers producing average software with average impact, average output is acceptable.
Which reminds me of when we were admonished to continue using assembly, lest our "real" skills atrophy from too much cushy C development.
Which reminds me of when we were admonished to keep our scope and probe skills sharp, and read and understand the schematics of whatever computer we were on, lest we forget how to diagnose faults in its components.
Which reminds me of when we were admonished to practice calculating in our heads and keeping slide rule skills sharp, lest they atrophy to a calculator.
You don't need to "keep practicing" in order to maintain your understanding.
The best engineers know how our systems work down to more levels, but for average developers producing average software with average impact, average output is acceptable.