Obviously there are syntactical differences between YAGNI and KISS but I can't see any semantic differences between them. Are they really in essence just the same thing?
相关问题
- Concrete Types or Interfaces for return types?
- Decoupling vs YAGNI
- UML help C# Design Principles
- What's the difference between design patterns
- Does Scala's pattern matching violate the Open
相关文章
- UML help C# Design Principles
- Concrete Types or Interfaces for return types?
- Decoupling vs YAGNI
- UML help C# Design Principles
- What's the difference between design patterns
- Does Scala's pattern matching violate the Open
- Pipeline design pattern implementation
- Liskov substitution principle - no overriding/virt
Short: Yagni states you need to cut off the code you don’t need right now, KISS is about making the remaining code simple. Here’s how it can be visualized:
read more here
YAGNI (You aint gona need it) refers to over analyzing and implementing things that may or may not be needed. Sure algorithmic elegance is nice and all but most situation you dont need it. In general engineering terms you should be carefull not to include your own requirements so that you dont taint your customer needs with your own ideas that end up costing the project with little impact for the client.
KISS (Keep it simple stupid) refers to the fact that easy systems are easier to manage. Keeping things simple is not nesseserily less work (like YAGNI is) since it requires more knowlege to implement. They are sometimes similar but grow from different needs.
YAGNI grows from a too much future anticipation, overzealous workers if you may. KISS is a strategy that tries to counteract human tendency for design creep.