**Sometimes it is better to implement something without all the bells and whistles.** An evocative way to [[Simplicity]] is good - the phrase "**worse is better**" can be a guide when it comes to implementing features or functionality on a given application or class, or more generally in systems design. When you're coding it feels good sometimes to add features, even if it comes at the expense of [[Conceptual Integrity]], it can _feel_ good to have covered some oblique use case, even if [[YAGNI]]. In reality, it's usually better to do one thing, and do it well. _**That doesn't mean do one thing, and include all possible hypothetical features of that thing.**_ It's okay, and perhaps _better_, to let it "feel" worse. **** # More ## Source - Wikipedia article "worse is better" ## Related - [[More is Unnecessary, Less is Impossible.]] - [[Conceptual Integrity]] - [[Simple is Maintainable]] - [[The Zen of Python]]