DEV Community

Discussion on: The biggest mistake library and framework maintainers make

Collapse
 
burdettelamar profile image
Burdette Lamar

The more "library," (rather than "framework"), the harder it is to keep the user in view.

When I was developing vector-concurrent numerical functions, we had little idea how the customer would actually use them. So we just made them as bomb-proof as we could.

PS: If you think the use won't matter, think again. If we'd had some idea what values would be passed in, it would have let us do better optimization. Guessing may not be helpful: one user's optimization is another user's pessimization.

Collapse
 
dkamer profile image
David Joseph Kamer

Sometimes building a library w/o imposing requirements can lead to a modular peice of code that can be used in many more situations. There is a partial trade off between short term stability and long term reusibilty.