• Home
  • Blog
  • Projects
  • Bookshelf
  • About

Being Unopinionated






A quick will reveal that there's a lot of libraries and packages out there that brag about being unopinionated. I think that is a misnomer and instead all these libraries and packages are just differently-opinionated from the libraries/packages that they are alternatives for.

Published 📅:
Last modified 📝:

While it doesn't say so on their site, I feel like the original premise of was that it was an unopinionated monorepo manager. In reality, it just held different opinions about how tasks should be managed than tools like or .

If you're looking at adopting some library or package (or even an SaaS application) and one of the main selling points is about it being unopinionated, don't fall for it!

It's fine for a library to express some opinions about how it should be adopted and how the overall workflow/application in which it is adopted should function. However, it's false advertising to say that it is unopinionated.



Tags:

Loading...

Related Posts

micropost

Tip: Secrets for Cloudflare Workers

Published:

Tip: GitHub Created Date Filtering

Published:

Link: Next.js Is Infuriating

Published:

Dependabot Hell
← Back to all posts
micropost
GitHub search
turborepo
Share this post on Bluesky
See discussion on Bluesky
nx
lerna
....
....

Published: ....

Link: What the hell is going on right now?

Published: ....

....
....
....
Recipe: Horchata Protein Latte

Published: ....

Zombie Retros

Published: ....

Link: How I build software quickly

Published: ....

Vacation (and streaks)

Published: ....

Polish is Important

Published: ....

<Blank> Driven Development

Published: ....

All Documentation Should Be Dated

Published: ....

Adding Microposts

Published: ....

Service Monitors and Observability

Published: ....

Leveraging service monitors properly to improve service observability.

Stop Snacking

Published: ....

No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).

No Process is Invisible Process

Published: ....

Low/no process workflow wasn't actually no process, it was only an "invisible" process. An implicit contract with everyone on the team to do that async workflow on their own time.