[[Simplicity is Worth Effort]]. If you can write simple code, you should. When it comes to writing code, though, it's not always obvious (especially to newer coders) what *the simple thing* **actually** is. When coding, one [[Proxy Measures|proxy]] question you can use to gauge [[Simplicity]] is: > How easy is this to move? Have you built this such that you could change things easily? How [[Complect]]ed are its individual features & facets? **Note**: this applies to coding pretty specifically. If you're looking for designing *plans*, a good proxy is to [[Design systems Based on Simple Principles|prefer system design choices that can be explained using the fewest number of words.]]. ## Example ### Complex Function A calls B. Function B calls C. Function C calls D. ### Simple Function A, B, C, and D operate on a queue. Removing one (or inserting a new one) **doesn't require changing others.** ==This is the literal definition of "simple"== **** # More ## Source - https://www.youtube.com/watch?v=rI8tNMsozo0