Why do developers keep piling abstractions on top of abstractions? There is machine code. Then the assembler. Then the compiler, that targets the JVM. Then the

Why do developers keep piling abstractions on top of abstractions? There is machine code. Then the assembler. Then the compiler, that targets the JVM. Then the programming language. Then classes and objects. And then modules. And then design patterns. And then architectural patterns. Why all of this should exist? ... Well, because each level is intended to provide something the previous levels cannot provide. My last "operator" (not really an operator, but conceptually similar) is Airflow. Because Kubernetes doesn't have a way to chain job executions, as in "run this job after these two jobs finished".