Sebastian Fitzek’s Der Heimweg
Gebraucht kaufen
26,05 €
Lieferung für 4,75 € 6. - 24. Februar. Details
Gebraucht: Wie neu | Details
Verkauft von Paper Cavalier Deutschland
Zustand: Gebraucht: Wie neu
Kommentar: Neuwertiges, ungelesenes Exemplar! Lieferung voraussichtlich innerhalb von 2-3 Wochen.
Hinzugefügt zu

Es ist ein Fehler aufgetreten.

Es gab einen Fehler beim Abrufen deines Wunschzettels. Versuche es noch einmal.

Es ist ein Fehler aufgetreten.

Liste nicht verfügbar.
Bild des Kindle App-Logos

Lade die kostenlose Kindle-App herunter und lese deine Kindle-Bücher sofort auf deinem Smartphone, Tablet oder Computer – kein Kindle-Gerät erforderlich.

Mit Kindle für Web kannst du sofort in deinem Browser lesen.

Scanne den folgenden Code mit deiner Mobiltelefonkamera und lade die Kindle-App herunter.

QR-Code zum Herunterladen der Kindle App

Dem Autor folgen

Alan Cooper
Folgen
Ein Fehler ist aufgetreten. Wiederhole die Anfrage später noch einmal.

The Inmates Are Running the Asylum Gebundene Ausgabe – 1. April 1999

Englisch Ausgabe von Alan Cooper (Autor)
4,4 4,4 von 5 Sternen 343 Sternebewertungen
Alle Formate und Editionen anzeigen

Dieses Buch gibt es in einer neuen Auflage:

The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity
The Inmates Are Running the Asylum: Why High Tech Products Drive Us Crazy and How to Restore the Sanity
38,89 €
(343)
Nur noch 13 auf Lager (mehr ist unterwegs).
Armed with solutions to the dilemma of how dependent every one of us is becoming on electronic products, the author argues that, despite appearances, business executives are simply not in control of the high-tech industry. He explains how talented people continuously design bad technology-based products and uses his own work to show businesses of all sizes how to harness talent to create products that will both thrill users and grow the bottom line. Annotation c. by Book News, Inc., Portland, Or.
Vorherige Folie der Produktdetails
  1. Seitenzahl der Print-Ausgabe
    261 Seiten
  2. Sprache
    Englisch
  3. Herausgeber
    Sams Publishing
  4. Erscheinungstermin
    1. April 1999
  5. Abmessungen
    16.51 x 2.54 x 24.13 cm
  6. ISBN-10
    0672316498
  7. ISBN-13
    978-0672316494
  8. Alle Details anzeigen
Nächste Folie der Produktdetails
Beliebte Taschenbuch-Empfehlungen des Monats
Jetzt durch unsere Auswahl beliebter Bücher aus verschiedenen Genres wie Krimi, Thriller, historische Romane oder Liebesromane stöbern Hier stöbern

Produktbeschreibungen

Amazon.de

In this book about the darker side of technology's impact on our lives, Alan Cooper begins by explaining that unlike other devices throughout history, computers have a "meta function:" an unwanted, unforeseen option that users may accidentally invoke with what they thought was a normal keystroke. Cooper details many of these meta functions to explain his central thesis: programmers need to seriously reevaluate the many user-hostile concepts deeply embedded within the software development process.

Rather than provide users with a straightforward set of options, programmers often pile on the bells and whistles and ignore or deprioritize lingering bugs. For the average user, increased functionality is a great burden, adding to the recurrent chorus that plays, "computers are hard, mysterious, unwieldy things." (An average user, Cooper asserts, who doesn't think that way or who has memorized all the esoteric commands and now lords it over others, has simply been desensitized by too many years of badly designed software.)

Cooper's writing style is often overblown, with a pantheon of cutesy terminology (i.e., "dancing bearware") and insider back-patting. (When presenting software to Bill Gates, he reports that Gates replied: "How did you do that?" to which he writes, "I love stumping Bill!") More seriously, he is also unable to see beyond software development's importance--a sin he accuses programmers of throughout the book.

Even with that in mind, the central questions Cooper asks are too important to ignore: Are we making users happier? Are we improving the process by which they get work done? Are we making their work hours more effective? Cooper looks to programmers, business managers, and what he calls "interaction designers" to question current assumptions and mindsets. Plainly, he asserts that the goal of computer usage should be "not to make anyone feel stupid." Our distance from that goal reinforces the need to rethink entrenched priorities in software planning. --Jennifer Buckendorff

Über den Autor und weitere Mitwirkende

Alan Cooper is a software author and visionary whose industry credits include creating the visual programming interface for Microsoft's Visual Basic. His one-man crusade for better design in the '90s has evolved into the Cooper Interactive Design firm, which he founded in 1992. As an industry leader, he is frequently speaking at computer conferences such as VBITS as well as meeting with industry leaders to provide guidance and direction.

Produktinformation

  • Herausgeber ‏ : ‎ Sams Publishing; First Printing Edition (1. April 1999)
  • Sprache ‏ : ‎ Englisch
  • Gebundene Ausgabe ‏ : ‎ 261 Seiten
  • ISBN-10 ‏ : ‎ 0672316498
  • ISBN-13 ‏ : ‎ 978-0672316494
  • Abmessungen ‏ : ‎ 16.51 x 2.54 x 24.13 cm
  • Kundenrezensionen:
    4,4 4,4 von 5 Sternen 343 Sternebewertungen

Informationen zum Autor

Folge Autoren, um Neuigkeiten zu Veröffentlichungen und verbesserte Empfehlungen zu erhalten.
Alan Cooper

Alan Cooper

Brief content visible, double tap to read full content.
Full content visible, double tap to read brief content.

Entdecke weitere Bücher des Autors, sehe ähnliche Autoren, lese Buchempfehlungen und vieles mehr.

Kundenrezensionen

4,4 von 5 Sternen
343 weltweite Bewertungen

Dieses Produkt bewerten

Sag deine Meinung zu diesem Artikel
Kundenrezension verfassen

Spitzenrezensionen aus Deutschland

  • S. Herrlinger
    5,0 von 5 Sternen Just true.
    Bewertet in Deutschland am 17. Mai 2010
    Alan Cooper wonderfully describes many of the things I've been trying to articulate for years, now I have a written gospel I can pray to my executives. As a programmer you have to get that Software Design is not Interaction Design and it should never be done by one and the same person. This book doesn't want to take power away from the programmer, but make the world a little bit better by reducing the frustration software causes. As stated:
    "Badly designed business software makes people dislike their jobs. Their productivity suffers, errors creep into their work, they try to cheat the software, and they don't stay in the job very long. Losing employees is very expensive, not just in money but in disruption to the business, and the time lost can never be made up." True.
    If you ever heard something like "Don't throw out the prototype. Let's use it as the foundation for the real product." and felt bad about it, you will love the ideas in this book and finally have something you can point on with an outstretched arm and uplifted eyebrows. :O
    Nützlich
     Melden
  • Doug Briggs
    5,0 von 5 Sternen He has it right, but those who should read and heed won't.
    Bewertet in Deutschland am 27. April 1999
    Bells and whistles have become an addiction for software developers, and it's high time someone finally turned a spotlight on this aspect of software "development" that has crippled many an otherwise good program.
    QuickBooks was once a nice little bookkeeping program for small businesses. We used it for years, loved it, then upgraded to version 5.0. Unfortunately our old version was out the window before we discovered what a colossal mistake we'd made.
    First, there's the "User's Guide": almost a thousand pages! A manual of such bulk is a tipoff that a program is too complex for most mortals (assuming the text was reasonably to the point).
    Second, the addition of a multitude of new (and useless, for us) functions so cluttered the functionality of QuickBooks that we couldn't fathom how to use the functions that were once a breeze. We never did figure out how to customize the "new and improved" invoice template to accommodate our use.
    Third: "Features" would jump up and stand defiantly in our way. When trying to prepare invoices using the barely acceptable template we'd be interrupted with an error message that said we didn't have the item in stock -- we didn't want to use QuickBooks for inventory control, but no, QuickBooks insisted.
    After trying to beat some use out of QuickBooks we unloaded it and tossed it out. Now we use the invoice template that comes with MS Excel (INVOICE.XLT)and it works just fine. Intuit actually did us a favor by exercising their compulsion to ruin a simple program; they forced us to discover that a totally functional little invoice template, one infinitely customizable, was on our computer all the time. (Of course, the discovery made us ask ourselves why we weren't heads-up enough to simply design our own invoice using Excel in the first place!) It's easy to get carried away searching for special-use utilities instead of using the tools already right at hand to create our own -- free.
    Grammatik is another disaster. Once I considered it indispensable and proofed all my books on it to get the reading level down and identify potential improvements in style. But the folks at Grammatik couldn't leave it alone. New and useless features were added which only bogged down the process of using it. A speller was included(as if we didn't have spell-checking features in WordPerfect and Word!), and if there was a way to disable Grammatik's spell check I never found it. And what a sorry spell checker it was -- wouldn't allow you to add words to its inadequate vocabulary, wouldn't allow you to ignore all occurrences of words it didn't like, so it stopped on every usage of them.
    Where I once used Grammatik on entire books of, say, 200,000 words, the new "improved" version would drive me mad trying to get through a 5,000 word chapter. Out it went.
    I considered Norton Utilities indespensable for a decade. Now it's not loaded on a single machine here because it pokes its nose into too many places where it has no business, slinging DLLs around in reckless profusion, causing problems and lockups, not to mention its insatiable appetite for computer resources.
    If Microsoft can't deliver a Windows version without bugs, how can increasingly "function-rich" programs written by third parties work under Windows without causing conflicts? They can't, and they don't.
    Cooper is on the mark: The inmates are running the asylum, and they don't care what us mere users have to endure to accommodate their passions for excess.
    It was Mark Twain -- wasn't it? -- who apologized to a friend for writing such a long letter by explaining, "I didn't have time to write a short one." Brevity is hard work.
    We've solved many problems here by brutally pruning the utilities on our machines, then formatting hard drives to clear out all the DLLs and other files that have been left behind. A typical gain in available hard-drive space is about a third after a format and complete reload of programs and data files.
    Unfortunately, there are too many computer users who "think" they want bigger and better programs even if they never discover how to use more than their most basic features. Also, the computer press fawns over "feature rich" programs -- the journalists review them, but aren't saddled with using them every day. So vendors keep bloating bloating programs and raising the prices.
    I've hoped in vain that some enterprising software writers would follow along behind the big boys and create iterations of the simple, functional and easy-to-use utilities they've discarded.
    Maybe Cooper will inspire some to do just that.
    Doug Briggs
    Eine Person fand diese Informationen hilfreich
    Nützlich
     Melden
  • Theresa M. Flynn, Doctoral Student, Pepperdine University
    4,0 von 5 Sternen Blame it on Cognitive Friction
    Bewertet in Deutschland am 27. März 2000
    Alan Cooper makes the case for goal-directed interactive software design in his provocative book, The Inmates are Running the Asylum. He argues that though it would seem common sense, few software-based computer products are designed with the end-user in mind prior to their construction. Instead, they are all too often feature-laden "dancing bearware" that may impress the inexperienced, but infuriate them as well. Cooper suggests that software engineers are to blame for this phenomenon, identifies several examples of ill-conceived software engineering, and offers design specifications to ameliorate the problem.
    The real culprits in Cooper's book are the programmers and engineers who design products to work their way as opposed to the best way. Cooper argues that the approach that companies take in creating technological products is backward. They do not consider what customers want first. Rather, they consider what programmers can produce (what's capable) and what business people can sell (what's viable), rather than what customers want and need (what's desirable).
    Examples abound throughout the book illustrating the frustrating results of such backward engineering. These vary from the tragic to the mundane. The first page of the book details a fatal plane crash which could have been prevented had the pilot's computer been programmed to account for human error in navigational commands. Later in the book, Cooper proposes simplified VCR design that would eliminate universal frustration with programming one's VCR, not to mention eliminate the ubiquitous flashing 12:00!
    Clearly airplane accidents, if not VCR ineffectuality, concern most people. How can computer manufacturers design the most desirable products to avoid such public danger or distress? Cooper outlines specifications that require goal-directed design and end-user orientation. Software engineers typically design programs to accomplish tasks, e.g. the aforementioned navigational computer was programmed to direct the plane where the pilot commanded it. That was its task.
    Unfortunately, the pilot commanded it to fly into a granite mountain. Had the computer been goal-directed designed, i.e. programmed to direct the plane where the pilot commands it, given that such directions do not result in a collision, tragedy would have been avoided. The latter case illustrates end-user orientation, for it allows for pilot fatigue, emotion, latitudinal unfamiliarity, or oversight, any of which may occur on a given flight.
    Cooper's call for goal-directed design and end-user orientation of software-based computer products is compelling and seemingly common sense. Overall the book is well written and includes memorable examples and convincing arguments. One less cogent claim, however, is Cooper's suggestion that technology apologists will play an important part in affecting change toward goal-directed interactive software design. I assert that change must come from within the programming and engineering ranks. Apologists, by definition, are not cohesive or likely to take a stand against that which they're apologizing for. This is like asking an enabler to seek help for an alcoholic. It is not going to happen. The software engineers must lay down their addiction to bells and whistles, tasks and tortuous interfaces, and see through the eyes of the end-user: you, me, and the other 98% of the world with flashing 12:00s on our VCRs.
    Nützlich
     Melden

Spitzenrezensionen aus anderen Ländern

Alle Rezensionen ins Deutsche übersetzen
  • V K HAMEED
    5,0 von 5 Sternen A really important read on the craft of software development
    Bewertet in Indien am 21. Januar 2022
    Verifizierter Kauf
    This book emphasize on the importance of Interaction design while creating software. It was an eye opening read that really helped with giving more depth on the craft of designing systems.
    Melden
  • iAPX
    5,0 von 5 Sternen A must-read for Web designers, Developers, Product Owners, Project Managers and Managers!
    Bewertet in Kanada am 6. März 2016
    Verifizierter Kauf
    As a professional developer since nearly 30 years, I have designed "Interfaces" (Interactions in fact) and built them. I was really proud of it.

    This book show me how wrong I was, and even if my Interactions and Interface wasn't too catastrophic, they weren't as good as they needed to, and that I have to re-learn everything about Interaction Design, because sadly I usually work without Interaction Design team. So I have to learn, to take time (even spare-time if necessary) to design before coding, even if it will be still imperfect, it will always be better than coding first then trying to trick an already created interaction.
    Melden
  • Carlo Beschi
    5,0 von 5 Sternen the inmates are (still) running the asylum ...?
    Bewertet in Italien am 18. Oktober 2013
    Verifizierter Kauf
    Wow. First published in 2006. Waited way to long in my reading list ... A must read for almost all IT product development professionals - especially for engeneers, and their managers.
    The design of the product, and of the way the user may interact with it, as something which MUST be given the proper attention, the right placement in the production lifecycle and which requires sincere domain experts (interaction designers).
    Many companies are possibly in a far better situation than in 2006, regarding this topic - others are definitely not.
    A great book, easy to read, full of irony, and seminal for new (in 2006) concepts and tools, such as the usage of personas.
    Melden
  • M. Mallia
    5,0 von 5 Sternen Great book!
    Bewertet in Großbritannien am 31. Dezember 2010
    Verifizierter Kauf
    In this book Alan Cooper efficiently illustrates the accurate point that users don't often know what they want when designing a system.

    If you are involved in designing systems in any way or are simply interested in the concept, this book is a must have read!

    This product is not just an interesting book, it is also a very useful tool.
    Melden
  • C. Rouge
    5,0 von 5 Sternen Lecture essentielle pour qui travaille dans la conception et le développement d'applis numériques
    Bewertet in Frankreich am 20. Oktober 2008
    Verifizierter Kauf
    Voici un livre qui m'a immensemment soulagé, tant il confirmait les impressions que j'avais en travaillant avec des ingénieurs informatiques sur différents projets. Ce n'était donc pas que moi, pourtant très technophile, mais pas ingénieure pour autant!

    Résumé:

    Les applis informatiques sont à présent partout: depuis nos radios réveil jusqu'aux systèmes de chauffage de nos maison, sans parler de nos environnements de bureau. Or, ces applis ne sont pas conçues AU SERVICE de l'utilisateur ( ou -trice) mais selon la vision de monde des informaticiens, qui elle meme dérive de la façon dont fonctionne un ordinateur. C'est à dire qu'elles demandent à l'utilisatrice de s'adapter au language machine plutot que d'adapter le language machine à l'utilisateur..
    Petit souci, qui explique le blocage que beaucoup font face à l'informatique.

    L'auteur analyse la façon dont sont développées ces applis pour expliquer pourquoi l'on constate ceci aujourd'hui. Il montre enfin comment développer des applis au service de l'utilisateur final et non des développeurs informatique.

    Quelques points:

    L'ordinateur pense comme une machine, de façon précise et méthodique. L''etre humain pense de façon vague, par généralités, et de façon plus intuitive que méthodique.
    Les informaticiens développent en calquant la façon de faire de la machine plutot que de partir de la façon de fonctionner de l'utilisatrice finale.

    Il fait la distinction entre l'homo sapiens, l'individu de base, et l'homo logicus, l'informaticien.
    L'un adore se simplifier la vie, l'autre adore décortiquer la complexité plus que de se simplifier la vie. Il est plus intéressé par le process intellectuel que par le résultat final censé apporter un bien à l'utilisatrice.

    Lisez le, c'est très instructif et essentiel pour développer des bonnes applications pour tous, pas uniquement pour les ' fans de technos '!

    San Francisco Consulting
    Melden