3 ms·
Great article. To expand a little on why “Keep It Simple” is so powerful: less code = less bugs and less security issues. Less code = easier to change.
by davedx 4y ago
Great article.
To expand a little on why “Keep It Simple” is so powerful: less code = less bugs and less security issues. Less code = easier to change.
- anticristi 4y agoAlso cleverness is overrated. You might be able to be clever once, but mid-term you will struggle to keep up with "collective cleverness". Sure today you might implement a better authentication code than the one offered in your favorite framework, but will you keep up with the new cleverness that will pour into the framework tomorrow?
- muglug 4y agoI don't think less code = less security issues. Often using those secure-by-default frameworks require more code. The simplest example in PHP (highlighted in the article for its default-insecurity): echo '<h1>Hello ' . $_GET['name'] . '</h1>'; is vulnerable to XSS. echo '<h1>Hello ' . htmlentities($_GET['name']) . '</h1>'; is not vulnerable
- UK-Al05 4y agoLess code and simple are not often related.
- TheCondor 4y agoI’ll go much further… I think it creates severe cultural problems. It creates the belief that problems are more difficult than they might be, it creates the belief that a particular solution may be more valuable than it actually is, and then it biases future team expansion and retention. Perhaps more ultimately, if the complexity creeps in before the real challenge gets do, it radically affects the team’s ability to reason about it.