|
|
|
|
|
|
by mooreds
697 days ago
|
|
|
YAGNI includes time to fix things when YNI (you need it). YAGNI is not prematurely optimizing for complexity. If a PM (or an eng for that matter) can justify the need for the complexity, either because they are extracting 2-3 use cases in to a generalizable solution, or they have 1 but know that 2-3 or more are coming real soon, then bring on the complexity. It's a balance, for sure. |
|
|