CodeHistory.org https://validator.w3.org/feed/docs/rss2.html American Airlines Flight 965: The FMS Waypoint Ambiguity That Sent a 757 Toward a Mountain Air France 447: Automation Mode Confusion After the Pitot Tubes Iced Hawaii’s 2018 False Missile Alert: The Interface That Put a Real Alert Next to a Drill USS John S. McCain: Touchscreen Steering Controls and a Fatal Loss of Situational Awareness Citibank’s $900 Million Revlon Transfer: The Interface Workflow Behind an Accidental Payment Tesla Autopilot and the 2016 Williston Crash: Driver Monitoring, Automation, and Misunderstood Authority USS Vincennes: Aegis Displays, Identification, and the Limits of Automated Combat Information NORAD 1979: The Training Tape That Made Nuclear War Look Real Stanislav Petrov and the 1983 Soviet False Alarm: When the Computer Said the Missiles Were Coming Three Mile Island: Alarm Flooding and the Control-Room Interface That Obscured the Emergency Meta Galactica: The Scientific Language Model Withdrawn After Three Days Air Canada’s Chatbot Case: When a Company Was Held Responsible for Hallucinated Policy Google Gemini Image Generation 2024: When Safety Tuning Produced Historically Inaccurate Results UK A-Level Grading 2020: The Algorithm That Standardized Away Individual Outcomes Google Photos and the Gorilla Label: When Image Recognition Produced a Racist Failure Amazon’s Recruiting Model: The Hiring Algorithm That Learned Gender Bias from Historical Data IBM Watson for Oncology: When AI Marketing Outran Clinical Evidence COMPAS and Recidivism Scoring: The Fight Over Bias, Calibration, and Automated Justice Zillow Offers: The Pricing Model That Could Not Tame a Volatile Housing Market Microsoft Tay: How a Chatbot Learned the Worst Lessons of Twitter in Less Than a Day Ubuntu Touch: The Convergence Vision That Canonical Abandoned Project Ara: Google’s Modular Phone That Never Reached Consumers Nokia N-Gage: When Phone Software and Game Hardware Produced the Wrong Experience Windows Phone: The App-Gap Failure That Hardware Quality Could Not Fix Firefox OS: The Open Web Phone That Could Not Build a Device Ecosystem Amazon Fire Phone: The Device Strategy Built Around the Wrong Differentiators Nokia Symbian: How Technical Debt and Platform Fragmentation Weakened a Smartphone Giant Microsoft Kin: The Social Phone Platform Cancelled After Six Weeks webOS and Palm: A Brilliant Mobile Platform That Could Not Survive Its Market BlackBerry 10: The Modern Rewrite That Arrived After the Market Had Moved No Man’s Sky 2016: The Launch Gap Between Shipped Software and Public Expectations Battlefield 2042: The Live-Service Launch That Missed Technical and Community Expectations Cyberpunk 2077: The Console Launch That Triggered Refunds and a PlayStation Store Removal Fallout 76: The Online Transition That Launched with Bugs and Broken Trust Assassin’s Creed Unity: The Buggy Launch That Damaged a Flagship Franchise Batman: Arkham Knight on PC: The Port So Broken It Was Pulled from Sale Battlefield 4: The Launch Bugs That Forced DICE to Pause Future Projects SimCity 2013: The Always-Online Launch That Turned Server Capacity into Game Design Final Fantasy XIV 1.0: The MMO So Troubled Square Enix Shut It Down and Rebuilt It Diablo III and Error 37: When Always-Online Authentication Met Launch Demand Apple Maps 2012: The Data and Quality Failure Behind a Rare Public Apology PlayStation 3’s ApocalyPS3: The Clock Bug That Locked Users Out on March 1, 2010 Google Wave: The Collaboration Platform Whose Complexity Outran User Adoption Digg v4: The Redesign That Broke the Community and the Product Windows 10 October 2018 Update: The Release That Deleted Some Users’ Files Microsoft Zune 2008: The Leap-Year Bug That Froze Every 30GB Player MobileMe 2008: Apple’s Cloud Launch That Steve Jobs Publicly Called a Mistake Twitter’s Fail Whale Years: Scaling a Social Network Faster Than Its Architecture Home Journal