• Home
  • Welcome to the Jungle
  • Elements of Modern C++ Style
  • About

Sutter’s Mill

Herb Sutter on software, hardware, and concurrency

Feeds:
Posts
Comments
« Reader Q&A: What does it mean for [[attributes]] to affect language semantics?
We want await! A C# talk that’s applicable to C++ »

The ‘Of Course’ Principle of Design

2012-04-06 by Herb Sutter

Nicely put… Christian Lindholm:

Most companies (including web startups), he said, are looking to “wow” with their products, when in reality what they should be looking for is an “‘of course’ reaction from their users.”

Simple and obvious beats flashy. So many great designs are obvious in retrospect.

Hat tip to John Gruber.

Posted in Friday Thoughts | 4 Comments

4 Responses

  1. on 2012-04-09 at 8:07 am Mike

    “… in retrospect” being the key phrase. Turning that around:

    “Prediction is very difficult, especially about the future.”
    — Niels Bohr


  2. on 2012-04-11 at 7:59 am Herb Sutter

    @Mike: Yes, but my last sentence meant “obvious to *other* people in retrospect.” The designer who worked hard to understand his problem domain and design space could see it before it was there, and brought it into being.

    I think perhaps an even more apt quote here would instead be this from Alan Kay: “The best way to predict the future is to invent it.” Once invented, it’s obvious to everyone in retrospect that that’s what we needed to do — but it took a visionary to see that before it existed, and create it.


  3. on 2012-04-12 at 8:33 am ChuckEng

    Not sure I agree with that. I would say you can’t get to ‘Wow’ without ‘of-course’. And yes, too many folks try to go straight to ‘wow’. Don’t folks know writing software is difficult. Writing quality software is complex. Writing useful software is challenging. Writing ‘wow’ software is all the above + luck + favor of the gods + humility + discepline + focus ++… ;)


  4. on 2012-04-13 at 8:52 pm Jeffrey Bosboom

    The “of course” starts now!



Comments are closed.

  • Tweets

    • GotW #4: Class Mechanics (7/10): How good are you at the details of writing classes? This item focuses not onl... bit.ly/10TmyVQ 2 days ago
    • GotW #3 Solution: Using the Standard Library (or, Temporaries Revisited): Effective reuse is an important part... bit.ly/19zU1Uo 2 days ago
    • GotW #3: Using the Standard Library (or, Temporaries Revisited) (3/10): Effective reuse is an important part o... bit.ly/13TRX9o 6 days ago
    Follow @herbsutter
  • Popular

    • GotW #3 Solution: Using the Standard Library (or, Temporaries Revisited)
    • GotW #4: Class Mechanics (7/10)
    • GotW #1 Solution: Variable Initialization – or Is It?
  • Categories

    • Apple
    • C# / .NET
    • C++
    • Cloud
    • Concurrency
    • Effective Concurrency
    • Friday Thoughts
    • GotW
    • Hardware
    • Java
    • Microsoft
    • Opinion & Editorial
    • Reader Q&A
    • Software Development
    • Talks & Events
    • Uncategorized
    • Web

Blog at WordPress.com.

Theme: Customized MistyLook by WPThemes.


Follow

Get every new post delivered to your Inbox.

Join 1,389 other followers

Powered by WordPress.com