Abstraction
also: abstractions, abstracted, abstract away
Hiding complicated details behind a simple way to use them. You call "send email" without needing to know how email delivery actually works.
A simplified interface over more complex implementation details: a function, class or module that exposes what something does while hiding how. Good abstractions reduce what you need to know; premature or leaky ones add layers without simplifying anything.
A car's pedals and steering wheel. You drive without understanding fuel injection. If every car made you control the engine directly, driving would be much harder.
Agents love adding abstractions: wrappers, base classes, generic helpers. Some make code simpler; some just add layers to dig through. Knowing the word lets you ask, "Does this simplify, or just hide?"
I created a StorageProvider abstraction so we can switch from local files to S3 cloud storage later without changing the upload code.
Don't add a new abstraction layer for a single use. Keep it simple and direct until we actually need a second payment provider.
Thinking more abstraction is always better design. An abstraction with only one user often adds complexity without benefit.