Some developers, when presented with a new library, immediately say “We need...
Some developers, when presented with a new library, immediately say “We need to build an abstraction around this before we use it.”
You don’t know what abstractions make sense yet! And you may not need an abstraction at all.
Avoid abstracting things you haven’t used yet.
Years ago we started building our first page in Angular 1. An “over-abstractor” on the team said “We should abstract Angular so we can move to a different UI library later.”
What?!
Rule: It’s impossible to create a useful general abstraction for something that doesn’t exist.