Funny! I wrote the same article 6 years ago: <a href="https://www.dein.fr/2015-10-01-10-principles-for-good-code.html" rel="nofollow">https://www.dein.fr/2015-10-01-10-principles-for-good-code.h...</a>
Seems to be mixing up <i>software</i> with <i>code</i>.<p><pre><code> > 3. Good software is aesthetic
>
> Take a moment to step back and look at your code.
> It should look beautiful to you.
> ...
</code></pre>
It's not that the code quality doesn't matter, but this is just apples to oranges.
This submission broke the rules for "Show HN" - this is reading material, not a project people can try out and play with. We've taken "Show HN" out of the title now.<p><a href="https://news.ycombinator.com/showhn.html" rel="nofollow">https://news.ycombinator.com/showhn.html</a>
Love that!<p><i>> 8. Good software is thorough down to the last detail</i><p>That's my approach. It tends to earn me a bit of scorn, but I do it anyway.
Maybe I should add a few<p>1. <i>Good software is carefully balanced</i><p>a good software is created when the user requirements are carefully balanced against resource and time constraints.<p>2. <i>Good software is joyful to handle</i><p>A truly good software should invoke the child like playful and joyful instincts in the users.
There's one difference though. Unlike product designers, software engineers will never be in the spotlights. Not at Apple, anyway.<p>E.g. tell me how many times you've read an article about Jony Ive versus about an important software engineer at Apple.
Some of these apply better than others, but holy n4. That's the most necessary point of this post IMO.<p>`Code isn't "clever" if no-one understands it.`<p>It will make some code-bros mad though.
Amazing! I've just recommended Dieter Rams: As Little Design As Possible book on LinkedIn.<p>Good design is needed everywhere. It's much more than adding a gradient to a Buy button.
Prepares to be downvoted...<p>Why are these supposed to be special? Everyone would agree with these in theory but the problem is not lack of these principles, the problem is how to actually use them in a fast moving business with imperfect tools, imperfect knowledge, imperfect employees and changing goals.<p>If you looked at my systems, you might say I am not following the principles but I was and am, they just don't always work very well in real life.