The System Still Runs : Responsibility After Failure, Damage, and Irreversible Harm.DE

個数：

The System Still Runs : Responsibility After Failure, Damage, and Irreversible Harm.DE

  • 在庫がございません。海外の書籍取次会社を通じて出版社等からお取り寄せいたします。
    通常6～9週間ほどで発送の見込みですが、商品によってはさらに時間がかかることもございます。
    【重要ご説明事項】
    1. 納期遅延や、ご入手不能となる場合がございます。
    2. 複数冊ご注文の場合は、ご注文数量が揃ってからまとめて発送いたします。
    3. 美品のご指定は承りかねます。

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

Description

This book examines what responsibility looks like after failure has already occurred and damage cannot be undone. It explores how engineers, operators, and leaders inherit broken systems they did not design, must run them in degraded states, and make decisions where every option causes harm. Rather than focusing on prevention or optimism, the book addresses moral injury, accountability without justice, and the quiet labor of keeping systems running when stopping them is not possible. It is about living with irreversible consequences and continuing to act with integrity when repair is no longer available. 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.