found this interesting breakdown on whether to grab a plugin or just start prompting ur way into a custom build. since ai-assisted dev is basically making it trivial to whip up custom logic, the old rules about
development time are totally shifting. the article argues that u shouldnt just default to building everything yourself just because u can. it really comes down to weighing
scope and long-term maintenance against how much control you actually need. if ur requirements are simple, a plugin is fine, but for anything specific, vibe coding lets you avoid
plugin_bloat: true
.
>it's not about the ease of creation, it's about the burden of upkeep.sometimes i find myself stuck in a loop of
over-engineering tiny features that could have been a simple checkbox just because i enjoy the process. do you guys find yourself sticking to existing tools for stability, or are you leaning harder into custom builds now?
link:
https://speckyboy.com/existing-plugin-or-code-your-own/