> YAGNI is not an excuse to take lots of shortcuts against known good implementation patterns. I’d say it is, because “best practices” and “patterns” are usual

> YAGNI is not an excuse to take lots of shortcuts against known good implementation patterns. I’d say it is, because “best practices” and “patterns” are usually context dependent and will have a negative cost when applied when not needed.