Unnecessary complexity has a cost
Unnecessary complexity has a cost.
Take this blog for example. I’ve tried to keep it as simple as possible, both design-wise and in how it is built.
It uses a simple, custom HTML and CSS Hugo theme.
Really, nothing else is necessary for such a simple website. Anything else would be unnecessary complexity.
By keeping the technology for this website light, avoiding unnecessary complexity, it frees me to worry about what matters: the writing.
Perhaps what I’m looking for in terms of phrasing is: “ask whether the complexity is necessary and useful.” If it is, then go ahead. If there’s a doubt, keep it simple, because unnecessary complexity has a cost.