Principles for Better Design | Hacker News Reader

Principles for Better Design

reflexio.debec.eu

111 pointsNinroot25 comments

Summary:

1. Incremental improvement - implement a small version that works in a basic use case, then extend. Don't build it all in once.

2. Reuse code. Don't reinvent the wheel

3. Five whys - get to the root cause of why something should be done by asking yourself why many times. Understand the problem well before acting.

4. Keep the solution as simple as possible. Minimalization.

5. Perfection can't be reached, so don't aim there. Be as good as necessary.

6. Postpone complexity and introduce it only when really needed.

I completely agree with all of the above!

A nice short list of design principles/techniques. I'd also recommend The Design of Design [1] by Fred Brooks (of The Mythical Man-Month fame).

The article's final "Postpone Complexity" principle reminded me of Brooks' discussion of early vs. late decision binding. My main take-away is that there is a decision binding trade-off and we should not forget that early decision binding techniques (such as contracts, API specification, and cost quotes) have true value as well.

[1] https://en.wikipedia.org/wiki/The_Design_of_Design

My definition: Design is the process of giving 'form' to 'concept'.

The space of 'concept -> form' has many dimensions, with aethetics merely being a more contentious one. A set of 'principles for design' (or a school of design) takes a position on each dimension of this transitional space. (Constructibiliy is another dimension, for example. Cost is another. etc.)

It is interesting that OP noted the linguistic aspects of word design. A bit further East, linguistically "form" is distinguished from "image", with general notion of "drawing" rooted in the latter.

The stated principles are a mix of approaches and desirable attributes, but I think miss what to me is the core aspect of design that relates to achieving a specific stated goal within a time, cost and performance envelope. Or perhaps that’s perceived as ‘engineering’

I think engineering increasingly sees goals that aren't very specific or necessarily accurate, that change over time and where meeting them partially provides value. Thinking about engineering in terms of trading time, cost and performance or quality is one perspective but these things are often very hard to trade and focusing on providing value is usually more reliable.

> these things are often very hard to trade and focusing on providing value is usually more reliable

Good point and I completely agree. I just felt that not mentioning any of these things in an article on 'principles of design' understates the complexity of a real and principled design process.

Design is a broad topic. This post won’t approach the adjective qualifying a style with simple forms and a pure appearance. No. Design is broader than a sleek car or an harmonious living room.

Isn’t design more about usability/practicality than aesthetics?

Do they have to be mutually exclusive? The goal of design should be to solve a problem as elegantly as possible given the parameters of the problem and the tools/materials available. There is no reason a solution to a problem cannot be both practical and aesthetically pleasing.

In my opinion, I don’t think they should. The way I see it however is that if an object’s design is calculated in percentages: utility/practical/functionality should represent 80% of it, and aesthetics the remaining 20% (tngt: pareto’s law)

I think it's about both. A solution that solves a problem while also being aesthetically pleasing is better than one which only solves the problem.

That is a point of contention between different schools of thought. Industrialization, mechanical reproduction (manufacture) of objects, and corresponding jump in scale of production went hand in hand with emergence of "form follows function" as a principle of design for "Modern" design.

Now a quiz:

https://upload.wikimedia.org/wikipedia/commons/2/24/33._Witt...

Is that door by mr. uber rational Wittgenstein a specimen of form follows function, or do you note 'aesthetics' saying gutten tag there?

In my view, I would say the former.

Mostly agree, and no doubt that was the intent of LW: it is shorn of non-functional ornaments, but I propose that aesthetic choice determined the form of that door handle. Various forms would have worked.

I load this design article, and am immediately assaulted by full-width justified text -_-

They will fix it in the next iteration.

What is wrong with it? Works no matter the width. I like it. What do not you like about it? Serious question.

It’s hard to read. The space between words is not consistent and often too large.

Especially on narrow devices, the inconsistency of the lengths of white space is severe. Subjectively, I feel dizzy looking at the paragraphs on this site via my phone.

In print, full justification of text is done by more than just varying word spacing. It also involves varying tracking (letter spacing) on per-line basis, hyphenation and even very subtle character geometry adjustments.

Typesetting software does a lot of that magic automatically and further allows easy manual adjustments to make the copy look even and readable without awkward spacing, “corridors” etc. Browser handling and latest CSS capabilities don’t even come close.

Having studied typography and worked in typesetting, I can’t imagine using full justification of body copy on the web.

Also the author hasn't turned on hyphenation. It's a "rule" that when you justify text you should use hyphenation. If not, the spacing between words will be very uneven as can be seen in the text.

The author should try adding language to the HTML tag (`<html lang=en-US>`) and setting `hyphens: auto` in CSS. Still hyphenation in browser is of a lower quality than you will find in a book with good typesetting.

I played around with the page and, to me, left-aligned text looks much better than justified text.

It's a pretty terrible read on my mobile phone. The typeface is very thin and combined with the varying tracking and massive leading it's just hard to read.

Firdt off, the maximum line length should be between 50 and 80 characters roughly, not as many words as your display fits.

Justification instead of hyphens is also abhorrent and I don't know any justification (hehhehh) for why one should use it at all even. I know it's traditional in legal copy and sometimes in news papers but with proper hyphenation (which is possible with CSS these days) I would strongly recommend never to justify anything on the web if one can avoid it.

- justified paragraphs have been removed - html lang eng has been added - hyphens auto has been added

I feel like people always need something to criticize. the site has no models on load, clear content, good responsiveness, well written, etc... honestly it's a pretty good site.

I used to enjoy this place because the community expanded on the content that was posted, thus extending the life of the article. Instead, we've reached a point where people seem to be doing the opposite in the way of critique. I can understand comments that criticize the intricacies and theory of the content itself, because that does in fact lead to good discussions, but the more trivial complaints don't add anything substantial to the conversation and unnecessarily bloat up the comments.

Reply on news.ycombinator.com