Cliquer sur une vignette pour aller sur Google Books.
Chargement... Writing Is Designing: Words and the User Experiencepar Michael J. Metts
Aucun Chargement...
Inscrivez-vous à LibraryThing pour découvrir si vous aimerez ce livre Actuellement, il n'y a pas de discussions au sujet de ce livre. aucune critique | ajouter une critique
Without words, apps would be an unusable jumble of shapes and icons, while voice interfaces and chatbots wouldn't even exist. Words make software human-centered, and require just as much thought as the branding and code. This book will show you how to give your users clarity, test your words, and collaborate with your team. You'll see that writing is designing Aucune description trouvée dans une bibliothèque |
Discussion en coursAucun
Google Books — Chargement... GenresClassification décimale de Melvil (CDD)005.437Information Computer Science; Knowledge and Systems Computer programming, programs, data, security Systems programming and programs Systems programsClassification de la Bibliothèque du CongrèsÉvaluationMoyenne:
Est-ce vous ?Devenez un(e) auteur LibraryThing. |
***
It’s basically an advice book. It doesn’t lay down rules. Instead, it bridges the gap that often seems to exist between writers and designers.
If writers and designers worked together more, the book argues, both sides would benefit: writers would see writing as designing and designers would see writing as essential; none would exist without the other, not really.
Indeed, this book is quite the social book; the authors have taken a leaf from their own book and have communicated with a lot of different writers and designers to turn this out, which is a book that gives a lot of good to the writer-designer community.
One thing that I enjoyed about this book is how the main rule—if you can call it that—dictates that you must cooperate or perish, unless you’re perfect.
The authors believe that the key behind any successful product that has users should be listening to them, before, during, and after shipping. After all, most releases—especially in the software world—occur in cycles. If we don’t know our users, who does?
There are a lot of good tips in this book, for neophytes and experts alike.
Errors will always exist where humans also do. I recently logged this bug report with Microsoft when they’d written something incorrectly in their Writing Style Guide, which is adhered to by a lot of tech writers around the globe.
This means that not even the best and most experienced humans will spot errors: we all become blind to our own mistakes and this is, I find, most true when we are isolated, on our own or in teams.
This is why we need the help of others, be it users, peers, other company teams than our own, or just some AI bot.
The book does well with pointing out confirmation bias, where we subconsciously believe that we’re The One True Human Archetype. Personally, I’m light-skinned, male, and almost middle-aged. This means that I’m very privileged and should always be aware of this at any given time, really, when writing, as most other persons probably don’t view most worlds as I do.
We must strive to write for our intended audience:
There are a lot of examples throughout this book that all serve great purposes. I strongly recommend purchasing—or should one use ‘buy’, or even ‘get’?—a copy. ( )