to be much more efficient in dealing with all kinds of situations. It is also true that one can be effective without understanding what is below the abstraction as long as everything behaves nicely. So one should not pooh-pooh the notation of abstraction. On the contrary, one should celebrate it since allow us to be more efficient. 11 In fact, if we never have to combine a component with anything else into a larger system, and if nothing can go wrong with the component, then it is perfectly fine to understand this component only at the level of its abstraction. Introduction to Computing Systems: From Bits & Gates to C & Beyond, 2004 By Yale N. Patt, Sanjay J. Patel
have to combine multiple components into a larges system, we should be careful not to allow their abstractions to be the deepest level of understanding. If we don’t know the components below the level of abstractions, then we are at the mercy of them working together without our intervention. 12 If they don’t work together, and we are unable to go below the level of abstraction, we are stuck. Introduction to Computing Systems: From Bits & Gates to C & Beyond, 2004 By Yale N. Patt, Sanjay J. Patel And that is the state we should take care not to find ourselves in.
yourself! Don’t cheat the system! Be transparent! START IT! Automate it! This is about GitOps! In any moment of decision, the best thing you can do is the right thing, the next best thing is the wrong thing, and the worst thing you can do is nothing. Theodore Roosevelt https://en.wikipedia.org/wiki/Richard_Feynman