• Home
  • Blog
  • Projects
  • Bookshelf
  • About
← Back to all posts

Being Unopinionated

Published ....
Last modified ....

Share this post on BlueskySee discussion on Bluesky


A quick GitHub search 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.

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

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:

micropost

Loading...

Related Posts

micropost

Quick-Tip: Codex Chief of Staff Thread

....

Tip: Secrets for Cloudflare Workers

....

Tip: GitHub Created Date Filtering

....

Link: Next.js Is Infuriating

....

Dependabot Hell

....

Link: What the hell is going on right now?

....

Recipe: Horchata Protein Latte

....

Zombie Retros

....

Link: How I build software quickly

....

Vacation (and streaks)

....

Polish is Important

....

<Blank> Driven Development

....

All Documentation Should Be Dated

....

Adding Microposts

....

Service Monitors and Observability

....

Leveraging service monitors properly to improve service observability.

Stop Snacking

....

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

....

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.