[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-sOTEJN1F0QPp6C8mzA65KU2KZHyPgKTaeQhEKpUrsdE":3,"sanity-b2QnpdtBdIkkjwevulWTo_sT31mYtUwldEiKWukr168":197},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":172},[6],{"_id":7,"publishedAt":8,"slug":9,"sponsored":12,"title":13},"d81860b7-7b72-4ba5-8ad5-3b77fd9a8e9b","2026-07-14T07:40:00.000Z",{"_type":10,"current":11},"slug","your-ai-is-only-as-responsible-as-you-are",null,"Your AI is only as responsible as you are",[15,21,27,33],{"_id":16,"publishedAt":17,"slug":18,"title":20},"eb5b66eb-9410-4329-83bb-22bbff39402a","2026-04-28T13:00:00.000Z",{"_type":10,"current":19},"turn-scattered-knowledge-into-trusted-intelligence","Turning scattered knowledge into trusted intelligence: Stack Internal 2026.3",{"_id":22,"publishedAt":23,"slug":24,"title":26},"369c2401-b62e-4a37-8ff8-bf603023ecad","2026-03-02T15:03:00.988Z",{"_type":10,"current":25},"what-s-new-at-stack-overflow-march-2026","What’s new at Stack Overflow: March 2026",{"_id":28,"publishedAt":29,"slug":30,"title":32},"5e9053a4-07ea-447c-91ea-29e0b6228537","2026-02-02T15:00:00.000Z",{"_type":10,"current":31},"what-s-new-at-stack-overflow-february-2026","What’s new at Stack Overflow: February 2026",{"_id":34,"publishedAt":35,"slug":36,"title":38},"a1b538eb-a8a6-46d0-80a1-ac70ec9bb935","2026-01-05T10:00:00.000-05:00",{"_type":10,"current":37},"what-s-new-at-stack-overflow-january-2026","What’s new at Stack Overflow: January 2026",{"_createdAt":40,"_id":41,"_rev":42,"_type":43,"_updatedAt":44,"author":45,"body":59,"comments":148,"dateUrl":149,"excerpt":150,"legacyBody":151,"product":12,"publishedAt":154,"slug":155,"sponsored":12,"tags":157,"title":171,"visible":148},"2023-05-25T09:36:59Z","wp-post-3516","07ZbrKPSUrjrV4wQ6fICJv","blogPost","2023-07-13T14:54:26Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":51,"avatar":52,"employee":54,"name":55,"role":56,"slug":57},"2023-05-23T16:27:18Z","wp-author-114","07ZbrKPSUrjrV4wQ6fam8u","blogAuthor","2023-08-29T11:49:01Z",{"_type":53},"image","former","Jeff Atwood","Co-founder",{"current":58},"jeffatwood",[60,76,90,121],{"_key":61,"_type":62,"children":63,"markDefs":74,"style":75},"61c6f8c2b9c6","block",[64,69],{"_key":65,"_type":66,"marks":67,"text":68},"61c6f8c2b9c60","span",[],"We knew in our hearts this day would come: ",{"_key":70,"_type":66,"marks":71,"text":73},"61c6f8c2b9c61",[72],"em","Stack Overflow has defeated Google!",[],"normal",{"_key":77,"_type":62,"children":78,"markDefs":88,"style":89},"49abc01ef888",[79,83],{"_key":80,"_type":66,"marks":81,"text":82},"49abc01ef8880",[],"On July 2, from 6:45 AM PDT until 12:35 PM PDT, Google App Engine (App Engine) experienced an outage that ranged from partial to complete.\n\n\n\nFollowing is a timeline of events, an analysis of the technology and process failures, and a set of steps the team is committed to taking to prevent such an outage from happening again. The App Engine outage was due to complete unavailability of the datacenter's persistence layer, GFS, for approximately three hours.\n\n\n\nThe GFS failure was abrupt for reasons described below, and as a consequence the data belonging to App Engine applications remained resident on GFS servers and was unreachable during this period. Since needed application data was completely unreachable for a longer than expected time period, we could not follow the usual procedure of serving of App Engine applications from an alternate datacenter, because doing so would have resulted in inconsistent or unavailable data for applications.\n\n\n\nThe root cause of the outage was a bug in the GFS Master server caused by another client in the datacenter sending it an improperly formed filehandle which had not been safely sanitized on the server side, and ",{"_key":84,"_type":66,"marks":85,"text":87},"49abc01ef8881",[86],"strong","thus caused a stack overflow on the Master when processed.",[],"blockquote",{"_key":91,"_type":62,"children":92,"markDefs":115,"style":75},"3bab2d732af3",[93,97,102,106,111],{"_key":94,"_type":66,"marks":95,"text":96},"3bab2d732af30",[],"This is excerpted from ",{"_key":98,"_type":66,"marks":99,"text":101},"3bab2d732af31",[100],"2e5b19719950","a newsgroup posting by App Engine PM Chris Beckmann",{"_key":103,"_type":66,"marks":104,"text":105},"3bab2d732af32",[],", and was forwarded along to me by ",{"_key":107,"_type":66,"marks":108,"text":110},"3bab2d732af33",[109],"ccd6f51e7e55","Lenny Rachitsky",{"_key":112,"_type":66,"marks":113,"text":114},"3bab2d732af34",[],".",[116,119],{"_key":100,"_type":117,"href":118,"reference":12},"link","http:\u002F\u002Fgroups.google.com\u002Fgroup\u002Fgoogle-appengine\u002Fmsg\u002Fba95ded980c8c179",{"_key":109,"_type":117,"href":120,"reference":12},"http:\u002F\u002Fwww.transparentuptime.com\u002F",{"_key":122,"_type":62,"children":123,"markDefs":145,"style":75},"d385d56b70b0",[124,128,132,136,141],{"_key":125,"_type":66,"marks":126,"text":127},"d385d56b70b00",[],"In other, less amusing news, there will be ",{"_key":129,"_type":66,"marks":130,"text":131},"d385d56b70b01",[86],"no podcast this week",{"_key":133,"_type":66,"marks":134,"text":135},"d385d56b70b02",[],". But don't fret -- next week, we will have ",{"_key":137,"_type":66,"marks":138,"text":140},"d385d56b70b03",[139],"c9a067c54eb8","the ineffable Miguel de Icaza",{"_key":142,"_type":66,"marks":143,"text":144},"d385d56b70b04",[]," of Mono fame. Joel and I are both big fans, so this one should be fun.",[146],{"_key":139,"_type":117,"href":147,"reference":12},"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMiguel_de_Icaza",true,"2009\u002F07\u002F10","",{"code":152,"language":153},"\u003Cp>We knew in our hearts this day would come: \u003Cem>Stack Overflow has defeated Google!\u003C\u002Fem>\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>On July 2, from 6:45 AM PDT until 12:35 PM PDT, Google App Engine (App Engine) experienced an outage that ranged from partial to complete.\u003C\u002Fp>\n\u003Cp>Following is a timeline of events, an analysis of the technology and process failures, and a set of steps the team is committed to taking to prevent such an outage from happening again. The App Engine outage was due to complete unavailability of the datacenter's persistence layer, GFS, for approximately three hours. \u003C\u002Fp>\n\u003Cp>The GFS failure was abrupt for reasons described below, and as a consequence the data belonging to App Engine applications remained resident on GFS servers and was unreachable during this period. Since needed application data was completely unreachable for a longer than expected time period, we could not follow the usual procedure of serving of App Engine applications from an alternate datacenter, because doing so would have resulted in inconsistent or unavailable data for applications. \u003C\u002Fp>\n\u003Cp>The root cause of the outage was a bug in the GFS Master server caused by another client in the datacenter sending it an improperly formed filehandle which had not been safely sanitized on the server side, and \u003Cstrong>thus caused a stack overflow on the Master when processed.\u003C\u002Fstrong> \u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>This is excerpted from \u003Ca href=\"http:\u002F\u002Fgroups.google.com\u002Fgroup\u002Fgoogle-appengine\u002Fmsg\u002Fba95ded980c8c179\">a newsgroup posting by App Engine PM Chris Beckmann\u003C\u002Fa>, and was forwarded along to me by \u003Ca href=\"http:\u002F\u002Fwww.transparentuptime.com\u002F\">Lenny Rachitsky\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>In other, less amusing news, there will be \u003Cstrong>no podcast this week\u003C\u002Fstrong>. But don't fret -- next week, we will have \u003Ca href=\"http:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FMiguel_de_Icaza\">the ineffable Miguel de Icaza\u003C\u002Fa> of Mono fame. Joel and I are both big fans, so this one should be fun.\u003C\u002Fp>","html","2009-07-10T12:00:00.000Z",{"current":156},"this-just-in-stack-overflow-defeats-google",[158,166],{"_createdAt":159,"_id":160,"_rev":161,"_type":162,"_updatedAt":159,"slug":163,"title":165},"2023-05-23T16:43:21Z","wp-tagcat-background","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":164},"background","Background",{"_createdAt":159,"_id":167,"_rev":161,"_type":162,"_updatedAt":159,"slug":168,"title":170},"wp-tagcat-company",{"current":169},"company","Company","This Just In: Stack Overflow Defeats Google",[173,179,185,191],{"_id":174,"publishedAt":175,"slug":176,"sponsored":12,"title":178},"76c9771b-34e6-4d98-8641-ecefc711f0ef","2026-07-06T15:23:34.559Z",{"_type":10,"current":177},"when-the-sensor-starts-thinking-snortml-agentic-ai-and-the-evolving-architecture-of-intrusion-detection","When the sensor starts thinking: SnortML, agentic AI, and the evolving architecture of intrusion detection",{"_id":180,"publishedAt":181,"slug":182,"sponsored":12,"title":184},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":183},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":186,"publishedAt":187,"slug":188,"sponsored":12,"title":190},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":189},"your-ai-shipped-a-backend-that-boots-that-is-the-whole-problem","Your AI shipped a backend that boots. That is the whole problem.",{"_id":192,"publishedAt":193,"slug":194,"sponsored":12,"title":196},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":195},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"data":198,"sourceMap":-1},{"count":199,"lastTimestamp":12},0]