The abstraction ceiling is real and well-documented. Developers who use Docker cannot explain namespaces and cgroups. Developers who deploy to Kubernetes cannot configure iptables. Developers who write React cannot explain what the browser does with their code after the build step. Docker, as one engineer put it, "feels like magic until your container gets OOMKilled or you can't reach a port you swore was open. Then you realise you aren't running a mini-virtual machine; you're just running a process in a very fancy cage."
When the abstraction breaks, and it always does, they have no layer beneath to fall back to. The foundation was never taught. It was skipped. And skipping foundations does not save time. It borrows it, at interest.
HackerRank's 2025 report found that only 22% of developers are given time for learning and upskilling. 48% must find the time themselves. Employers are "unsure early-career developers can code without heavy AI assistance." The abstraction ceiling is not just a technical problem. It is becoming a hiring problem.
The Question
Dijkstra wrote: "Computer science is no more about computers than astronomy is about telescopes." He meant that the discipline is about thought, not machinery. One does wonder what he would make of a curriculum built entirely around the telescopes.
He also wrote: "Universities should not be afraid of teaching radical novelties; on the contrary, it is their calling to welcome the opportunity to do so. Their willingness to do so is our main safeguard against dictatorships, be they of the proletariat, of the scientific establishment, or of the corporate elite."
One does note the phrase "corporate elite" with a certain quiet interest.
What if we taught the protocol before the framework? The syscall before the container? The language before the library? What if proficiency meant understanding what happens beneath the abstraction, not merely operating the abstraction itself?
250,000 Kubernetes certifications were issued last year. One does wonder how many of them could explain what a process is.
Read the full article on vivianvoss.net →
By Vivian Voss — System Architect & Software Developer. Follow me on LinkedIn for daily technical writing.