> Effective code tends to put a lot of functionality behind a relatively small interface

Do you have actual strategies for reducing high surface-area:volume requirements into more easily managed low surface-area:volume code or is this just wishful thinking?

Nobody likes shim layers but they (and other horizontal strata) happen for a reason.