I suggest there are three types of layer that one passes through Abstraction - this thing of rare beauty Decision - often confused for abstraction and wrapper

I suggest there are three types of layer that one passes through Abstraction - this thing of rare beauty Decision - often confused for abstraction and wrapper, this is best thought of as a case statement in a function. They are wildly better in my opinion than lots of classes Wrapper - either fluff like getters and setters or placeholders for later decisions (acceptable) or weird classes and instances that the language affords but tend to be confusing - what is called indirection in the article Tools, utils, libraries - these are I classify as handles / affordances for other code to use - maybe they add layers but they add a single way in to the nice abstraction above.