Popular posts

I think "frameworks" involve abstracting workflow, like how construction workers will use scaffolding (an abstraction of a structure) to support them while they work on various parts of a building:

and "libraries" are closer to what they sound like: rather than being a collection of books, they're a collection of common solutions to problems. Just like how you might walk into a library and select just the right book to read you can use a code library like a bunch of pre-written solutions that you can look around for and select and put to use:

It's possible to make use of both frameworks and libraries, but you have to make sure that these solutions actually help what you're working on rather than making it awkward.

Picking the wrong framework is like having scaffolds that go to nowhere, but don't get you close what where you need to be to do your work. Picking the wrong library is like having a bunch of great solutions you don't need, and still not being able to find anything for what you do need.

Over time, you can build your own frameworks and put your own solutions into libraries that you can use when solving familiar problems.