Hacker News new | past | comments | ask | show | jobs | submit login

The difficulty of giving examples to illustrate what "clarity" means really shows in this article.

For the most part I evaluate software clarity by how many times I had to hit "goto definition" to see what was actually happening. But this takes us away from what the author was attempting to say. In my opinion, 95% of clarity comes down to writing good abstractions, and it is next to impossible to articulate what a good abstraction is.

It's like describing the taste of salt.




And even if one could articulate what a good abstraction is, someone would come along and disagree.


Because "good" just as "clear" is not universal. But we can actually estimate how good abstractions can be in specific circumstances for specific users if we think of them in terms of familiarity, simplicity, consistency, flexibility and universality.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: