This is a necessary part of creating more sophisticated systems. Abstracting the lower ends of complexity to focus on the higher ends. The problem is, of course

This is a necessary part of creating more sophisticated systems. Abstracting the lower ends of complexity to focus on the higher ends. The problem is, of course, when the abstractions leak and you need to debug a level lower than you're used to dealing. Still, I think that this is the best discussion on the matter [law of leaky abstractions](https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-abstractions/ https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a...). In the end, yes, it's best to understand everything all the way down to the thermodynamic processes that enable something to be produced, but you cut your losses at some point in order to get started. A leaky abstraction is when you are forced to learn, and how you discover that some of your assumptions are mistaken.