Thinking in User Experience for Engineers : Systems, Tradeoffs, and Human Trust

個数:

Thinking in User Experience for Engineers : Systems, Tradeoffs, and Human Trust

  • オンデマンド(OD/POD)版です。キャンセルは承れません。
  • 【入荷遅延について】
    世界情勢の影響により、海外からお取り寄せとなる洋書・洋古書の入荷が、表示している標準的な納期よりも遅延する場合がございます。
    おそれいりますが、あらかじめご了承くださいますようお願い申し上げます。
  • ◆画像の表紙や帯等は実物とは異なる場合があります。
  • ◆ウェブストアでの洋書販売価格は、弊社店舗等での販売価格とは異なります。
    また、洋書販売価格は、ご注文確定時点での日本円価格となります。
    ご注文確定後に、同じ洋書の販売価格が変動しても、それは反映されません。
  • 製本 Hardcover:ハードカバー版/ページ数 72 p.
  • 言語 ENG
  • 商品コード 9783384803313

Description

Thinking in User Experience for Engineers reframes user experience as a property of system behavior rather than a UI or design concern. The book examines how engineering decisions around latency, failure, state consistency, retries, recovery, and system boundaries directly shape user trust and behavior over time.Written for experienced engineers, it focuses on real production systems rather than visual design theory or UX frameworks. Through concrete scenarios and mental models, the book explains why good interfaces cannot compensate for unreliable system behavior, how users learn to distrust systems through repetition, and why recovery and predictability matter more than polish.This is a systems-first UX book for engineers responsible for building long-lived, trustworthy software. Abdelfattah Ragab is a senior software engineer focused on designing and building software systems that must operate reliably at scale and evolve over time. His work spans system architecture, performance, reliability, and long-term maintainability across modern web and backend technologies.He has experience working on complex production systems where correctness, clarity, and responsible decision-making matter more than short-term trends or tools. His writing focuses on helping experienced engineers develop stronger mental models, architectural judgment, and the ability to reason about tradeoffs in real-world software systems.Abdelfattah writes for professionals who are responsible not just for delivering features, but for shaping systems that must remain understandable, adaptable, and trustworthy as requirements and teams change.

最近チェックした商品