Keeping it simple, stupid. I'm writing a database for example and go out of my way to use conceptually simpler algorithms, even if they are slower. I use option

Keeping it simple, stupid. I'm writing a database for example and go out of my way to use conceptually simpler algorithms, even if they are slower. I use optional patches to refactor them. Ideally simplicity leads to adaptibility, simple things make less assumptions, and maintainability, it's easier to understand the behavior of simple things. That being said simplicity for it's own sake is not important, adaptibility and maintainability is what's important. Using a language that changes often and have a lot of subtlety or features, especially macros hurts maintainability, because one needs to understand the language first.