I build things with my hands. The human behind Shift - https://laravelshift.com, master of Git - https://gettinggit.com, and author of "BaseCode" - https://basecodefieldguide.com
YAGNI is really framework agnostic. One might argue you could call YAGNI on the use of a framework. However, I try not to call YAGNI on tooling - common tech among a team. That’s not to say their use should never be challenged, but YAGNI shouldn’t be the only motivation.
So, yes, YAGNI is something you practice regardless of tooling. In the case of a framework, you could use YAGNI as a motivation to stick closely with the conventions of the framework and not try to customize it too much.
YAGNI is really framework agnostic. One might argue you could call YAGNI on the use of a framework. However, I try not to call YAGNI on tooling - common tech among a team. That’s not to say their use should never be challenged, but YAGNI shouldn’t be the only motivation.
So, yes, YAGNI is something you practice regardless of tooling. In the case of a framework, you could use YAGNI as a motivation to stick closely with the conventions of the framework and not try to customize it too much.
YAGNI must work well with something like Sails.js then.
Thanks!