krapp 2 days ago

That book is talking about user interaction and application design, not development.

We absolutely should want developers to think.

Reply View 3 replies
  • crabmusket 2 days ago

    As experiments like TFA become more common, the argument will shift to whether anybody should think about anything at all.

    Reply View 2 replies
    • krapp a day ago

      What argument? I see a business model here, not an argument.

      Reply View 1 reply
      • crabmusket 11 hours ago

        I meant "the discourse", "the conversation we are all having", interpreting the experiment in TFA as an entry in that discourse.

        Reply View 0 replies
_se 2 days ago

This is such a massive misunderstanding of the book. Have you even read it? The developer needs to think so that the user doesn't have to...

Reply View 2 replies
  • finnborge 2 days ago

    My most charitable interpretation of the perceived misunderstanding is that the intent was to frame developers as "the user."

    This project would be the developer tool used to produce interactive tools for end users.

    More practically, it just redefines the developer's position; the developer and end-user are both "users". So the developer doesn't need to think AND the user doesn't need to think.

    Reply View 1 reply
    • stirfish 2 days ago

      I interpreted it like "why don't we simply eat the orphans"? It kind of works but it's absurd, so it's funny. I didn't think about it too hard though, because I'm on a computer.

      Reply View 0 replies