[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-TC9dZSVqFc8edX-eaCkEkYyo64UmhjXZNmc21I6pTdk":3,"sanity-weCGvfTbWXtDPrH8Abfs9ZChtOS4n3G_AOKBZCPl-8k":278},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":253},[6],{"_id":7,"publishedAt":8,"slug":9,"sponsored":12,"title":13},"f83eb5f0-1237-487f-84d8-f7abf2318c39","2026-06-25T07:40:00.000Z",{"_type":10,"current":11},"slug","code-isnt-causing-your-production-failures",null,"Code isn’t the only thing causing your production failures",[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":62,"comments":213,"dateUrl":214,"excerpt":194,"image":215,"legacyBody":218,"product":12,"publishedAt":221,"slug":222,"sponsored":12,"tags":224,"title":252,"visible":213},"2023-05-25T09:39:11Z","wp-post-9684","dgl3SCUzppW3U2LvCoSTGG","blogPost","2023-07-13T14:55:17Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":51,"avatar":52,"employee":57,"name":58,"role":59,"slug":60},"2023-05-23T16:27:18Z","wp-author-125","9HpbCsT2tq0xwozQflrfOh","blogAuthor","2023-08-30T13:15:26Z",{"_type":53,"asset":54},"image",{"_ref":55,"_type":56},"image-8c4101ec5a80bd817bd18a920b025b97dff07164-1022x1024-jpg","reference","former","Julia Silge","Data Scientist",{"current":61},"juliasilge",[63,163,182,190,195],{"_key":64,"_type":65,"children":66,"markDefs":144,"style":162},"103a6a118095","block",[67,72,77,81,86,90,95,99,104,108,113,117,122,126,131,135,140],{"_key":68,"_type":69,"marks":70,"text":71},"103a6a1180950","span",[],"For nine years, we at Stack Overflow have fielded a ",{"_key":73,"_type":69,"marks":74,"text":76},"103a6a1180951",[75],"433c5a973468","survey",{"_key":78,"_type":69,"marks":79,"text":80},"103a6a1180952",[],", asking people who code about their opinions on a variety of topics, from whether they prefer a ",{"_key":82,"_type":69,"marks":83,"text":85},"103a6a1180953",[84],"a0293a05891e","dark or light theme in their IDE",{"_key":87,"_type":69,"marks":88,"text":89},"103a6a1180954",[]," to ",{"_key":91,"_type":69,"marks":92,"text":94},"103a6a1180955",[93],"e0ece7692b04","how their challenges change with experience",{"_key":96,"_type":69,"marks":97,"text":98},"103a6a1180956",[],". This is a huge project for us each year, with contributions in 2019 from product managers, our UX researcher, designers, community managers, web developers, marketers, and me, Stack Overflow’s data scientist. We learn so much each year from our Developer Survey, both from the results and the process of fielding it; right now, we have a massive Google Doc of things to do better! One lesson that stands out is how important careful preparation is. Looking back at past years, we haven’t always been as successful at this as we’d like, but we’re proud of our progress on some challenging issues including survey design, data analysis reproducibility, and using language that connects with a broader population of developers.\n\nThere were three main folks involved in the planning of the actual survey questions and how you as a respondent engage with them. The first is ",{"_key":100,"_type":69,"marks":101,"text":103},"103a6a1180957",[102],"ce1f423af436","Anita Taylor",{"_key":105,"_type":69,"marks":106,"text":107},"103a6a1180958",[],", a product manager here at Stack Overflow who is leading the 2019 Developer Survey. “We try to incorporate as much feedback as we can from two audiences, the external developer community and internal Stack Overflow stakeholders,” Anita says. “Internally, we get input on proposed questions from dozens of Stack Overflow employees and then ask our engineers to take the survey and give us feedback. On the developer side, we did three things: reviewed direct feedback from last year's survey, took ",{"_key":109,"_type":69,"marks":110,"text":112},"103a6a1180959",[111],"76288f246e32","suggestions for new questions",{"_key":114,"_type":69,"marks":115,"text":116},"103a6a11809510",[],", and got input from 1,600 developers who took a test version of the survey.”\n\nAnita also is responsible for managing the technical details of how respondents interact with our survey. We experienced a few hiccups in this area because of the third-party survey platform we use, such as geographical challenges and ad-blocker issues, and we are exploring options for future surveys.\n\nThe second main person involved in planning the Developer Survey this year is ",{"_key":118,"_type":69,"marks":119,"text":121},"103a6a11809511",[120],"5c122c5b98c3","Beth Devine",{"_key":123,"_type":69,"marks":124,"text":125},"103a6a11809512",[],", Stack Overflow’s UX researcher. Beth’s deep user research experience has contributed to some significant improvements in question and survey design this year. “I was lucky to come on board with a great survey from 2018 to work from, but one of our biggest priorities this year was trimming the survey length,” says Beth. “Last year people overwhelmingly said it was too long.” It turns out this was harder than those of us planning the survey expected! “It’s a delicate balance between respecting that feedback and trying to make room for all the questions we’d like to ask,” Beth shares. “One solution was to identify questions and topics that had very consistent responses over the past few years. We realized that we weren’t learning a lot of new information, and that asking them every other year might be a better use of space. It still allows us to track trends in the data over time.” Last years’ median time to finish clocked in at almost 30 minutes. We successfully shortened it this year, without sacrificing too much, and as of today, this year’s respondents are finishing with a median time of 23 minutes.\n\nThe third main person involved in planning the 2019 survey is me, Stack Overflow’s data scientist. I worked with Beth in detail on question writing, so that our expectations for data analysis were aligned. I also used data from ",{"_key":127,"_type":69,"marks":128,"text":130},"103a6a11809513",[129],"1f8a60485a0a","last year’s survey",{"_key":132,"_type":69,"marks":133,"text":134},"103a6a11809514",[]," and trends in tags on our site (such as those visualized in our ",{"_key":136,"_type":69,"marks":137,"text":139},"103a6a11809515",[138],"a331491c7f34","Trends",{"_key":141,"_type":69,"marks":142,"text":143},"103a6a11809516",[]," tool) to choose which technologies to include on the survey. We wanted to include the most popular and fastest growing technologies without overwhelming the respondent with an extremely onerous list to scroll through. I used the write-in options from last year to check out technologies we may have missed, and we carefully considered which smaller or shrinking technologies we would be comfortable leaving off this year. If we cut one of your favorite technologies, a) I’m really sorry and b) please do write it in the text box!\n\n",[145,148,150,152,154,156,158,160],{"_key":75,"_type":146,"href":147,"reference":12},"link","https://stackoverflow.com/dev-survey/start?utm_medium=so-blog&utm_source=so-owned&utm_campaign=dev-survey-2019",{"_key":84,"_type":146,"href":149,"reference":12},"https://insights.stackoverflow.com/survey/2015#tech-ide",{"_key":93,"_type":146,"href":151,"reference":12},"https://insights.stackoverflow.com/survey/2016#challenges-change-with-experience",{"_key":102,"_type":146,"href":153,"reference":12},"https://www.linkedin.com/in/anitataylor/",{"_key":111,"_type":146,"href":155,"reference":12},"https://meta.stackoverflow.com/questions/375907/developer-survey-2019-any-topic-suggestions",{"_key":120,"_type":146,"href":157,"reference":12},"https://medium.com/@beth_ux/researchops-spotlight-beth-devine-user-researcher-at-stack-overflow-3c10766e860a",{"_key":129,"_type":146,"href":159,"reference":12},"https://insights.stackoverflow.com/survey/2018",{"_key":138,"_type":146,"href":161,"reference":12},"https://insights.stackoverflow.com/trends","normal",{"_key":164,"_type":65,"children":165,"markDefs":179,"style":181},"57edd8190363",[166,170,175],{"_key":167,"_type":69,"marks":168,"text":169},"57edd81903630",[],"So the ",{"_key":171,"_type":69,"marks":172,"text":174},"57edd81903631",[173],"adbef18c35ee","2019 Developer Survey",{"_key":176,"_type":69,"marks":177,"text":178},"57edd81903632",[]," is live now but for only a few more days -- take it before it closes!\n\n",[180],{"_key":173,"_type":146,"href":147,"reference":12},"h2",{"_key":183,"_type":65,"children":184,"markDefs":189,"style":162},"abfd5220c700",[185],{"_key":186,"_type":69,"marks":187,"text":188},"abfd5220c7000",[],"The final question on the survey this year is, “Do you have any feedback or thoughts you’d like to share?” What are people saying so far?\n\n",[],{"_key":191,"_type":53,"alt":12,"asset":192,"caption":194,"markDefs":12},"60265105ca96",{"_ref":193,"_type":56},"image-a40cdad2eb8177ccaaa6af11a02e047910818604-844x675-png","",{"_key":196,"_type":65,"children":197,"markDefs":211,"style":162},"3474bcf6d5de",[198,202,207],{"_key":199,"_type":69,"marks":200,"text":201},"3474bcf6d5de0",[],"We're doing our best to capture the opinions of everyone who codes, everywhere, so if you have a friend, family member, or colleague who codes but isn't a registered Stack Overflow user, or is just getting started with coding, please ",{"_key":203,"_type":69,"marks":204,"text":206},"3474bcf6d5de1",[205],"1a2436d62baa","send the survey their way",{"_key":208,"_type":69,"marks":209,"text":210},"3474bcf6d5de2",[],"!",[212],{"_key":205,"_type":146,"href":147,"reference":12},true,"2019/02/07",{"_type":53,"asset":216},{"_ref":217,"_type":56},"image-65b1d2dd60904875c11c6233d58ac3502e3a19f5-1921x1081-png",{"code":219,"language":220},"\u003C!-- wp:paragraph -->\nFor nine years, we at Stack Overflow have fielded a \u003Ca href=\"https://stackoverflow.com/dev-survey/start?utm_medium=so-blog&utm_source=so-owned&utm_campaign=dev-survey-2019\">survey\u003C/a>, asking people who code about their opinions on a variety of topics, from whether they prefer a \u003Ca href=\"https://insights.stackoverflow.com/survey/2015#tech-ide\">dark or light theme in their IDE\u003C/a> to \u003Ca href=\"https://insights.stackoverflow.com/survey/2016#challenges-change-with-experience\">how their challenges change with experience\u003C/a>. This is a huge project for us each year, with contributions in 2019 from product managers, our UX researcher, designers, community managers, web developers, marketers, and me, Stack Overflow’s data scientist. We learn so much each year from our Developer Survey, both from the results and the process of fielding it; right now, we have a massive Google Doc of things to do better! One lesson that stands out is how important careful preparation is. Looking back at past years, we haven’t always been as successful at this as we’d like, but we’re proud of our progress on some challenging issues including survey design, data analysis reproducibility, and using language that connects with a broader population of developers.\u003Cbr>\u003Cbr>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\nThere were three main folks involved in the planning of the actual survey questions and how you as a respondent engage with them. The first is \u003Ca href=\"https://www.linkedin.com/in/anitataylor/\">Anita Taylor\u003C/a>, a product manager here at Stack Overflow who is leading the 2019 Developer Survey. “We try to incorporate as much feedback as we can from two audiences, the external developer community and internal Stack Overflow stakeholders,” Anita says. “Internally, we get input on proposed questions from dozens of Stack Overflow employees and then ask our engineers to take the survey and give us feedback. On the developer side, we did three things: reviewed direct feedback from last year's survey, took \u003Ca href=\"https://meta.stackoverflow.com/questions/375907/developer-survey-2019-any-topic-suggestions\">suggestions for new questions\u003C/a>, and got input from 1,600 developers who took a test version of the survey.”\u003Cbr>\u003Cbr>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\nAnita also is responsible for managing the technical details of how respondents interact with our survey. We experienced a few hiccups in this area because of the third-party survey platform we use, such as geographical challenges and ad-blocker issues, and we are exploring options for future surveys.\u003Cbr>\u003Cbr>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\nThe second main person involved in planning the Developer Survey this year is \u003Ca href=\"https://medium.com/@beth_ux/researchops-spotlight-beth-devine-user-researcher-at-stack-overflow-3c10766e860a\">Beth Devine\u003C/a>, Stack Overflow’s UX researcher. Beth’s deep user research experience has contributed to some significant improvements in question and survey design this year. “I was lucky to come on board with a great survey from 2018 to work from, but one of our biggest priorities this year was trimming the survey length,” says Beth. “Last year people overwhelmingly said it was too long.” It turns out this was harder than those of us planning the survey expected! “It’s a delicate balance between respecting that feedback and trying to make room for all the questions we’d like to ask,” Beth shares. “One solution was to identify questions and topics that had very consistent responses over the past few years. We realized that we weren’t learning a lot of new information, and that asking them every other year might be a better use of space. It still allows us to track trends in the data over time.” Last years’ median time to finish clocked in at almost 30 minutes. We successfully shortened it this year, without sacrificing too much, and as of today, this year’s respondents are finishing with a median time of 23 minutes.\u003Cbr>\u003Cbr>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:paragraph -->\nThe third main person involved in planning the 2019 survey is me, Stack Overflow’s data scientist. I worked with Beth in detail on question writing, so that our expectations for data analysis were aligned. I also used data from \u003Ca href=\"https://insights.stackoverflow.com/survey/2018\">last year’s survey\u003C/a> and trends in tags on our site (such as those visualized in our \u003Ca href=\"https://insights.stackoverflow.com/trends\">Trends\u003C/a> tool) to choose which technologies to include on the survey. We wanted to include the most popular and fastest growing technologies without overwhelming the respondent with an extremely onerous list to scroll through. I used the write-in options from last year to check out technologies we may have missed, and we carefully considered which smaller or shrinking technologies we would be comfortable leaving off this year. If we cut one of your favorite technologies, a) I’m really sorry and b) please do write it in the text box!\u003Cbr>\u003Cbr>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:heading -->\n\n\u003Ch2>So the \u003Ca href=\"https://stackoverflow.com/dev-survey/start?utm_medium=so-blog&utm_source=so-owned&utm_campaign=dev-survey-2019\">2019 Developer Survey\u003C/a> is live now but for only a few more days -- take it before it closes!\u003Cbr>\u003Cbr>\u003C/h2>\n\n\u003C!-- /wp:heading -->\n\n\u003C!-- wp:paragraph -->\nThe final question on the survey this year is, “Do you have any feedback or thoughts you’d like to share?” What are people saying so far?\u003Cbr>\u003Cbr>\n\u003C!-- /wp:paragraph -->\n\n\u003C!-- wp:image {\"id\":9691} -->\n\u003Cfigure class=\"wp-block-image\">\u003Cimg src=\"https://stackoverflow.blog/wp-content/uploads/2019/02/initial_feedback-844x675.png\" alt=\"\" class=\"wp-image-9691\"/>\u003C/figure>\n\u003C!-- /wp:image -->\n\n\u003C!-- wp:paragraph -->\nWe're doing our best to capture the opinions of everyone who codes, everywhere, so if you have a friend, family member, or colleague who codes but isn't a registered Stack Overflow user, or is just getting started with coding, please \u003Ca href=\"https://stackoverflow.com/dev-survey/start?utm_medium=so-blog&utm_source=so-owned&utm_campaign=dev-survey-2019\">send the survey their way\u003C/a>!\n\u003C!-- /wp:paragraph -->","html","2019-02-07T15:08:00.000Z",{"current":223},"how-the-2019-stack-overflow-developer-survey-came-to-be-and-your-last-chance-to-take-it",[225,233,238,243,248],{"_createdAt":226,"_id":227,"_rev":228,"_type":229,"_updatedAt":226,"slug":230,"title":232},"2023-05-23T16:43:21Z","wp-tagcat-announcements","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":231},"announcements","Announcements",{"_createdAt":226,"_id":234,"_rev":228,"_type":229,"_updatedAt":226,"slug":235,"title":237},"wp-tagcat-code-for-a-living",{"current":236},"code-for-a-living","Code for a Living",{"_createdAt":226,"_id":239,"_rev":228,"_type":229,"_updatedAt":226,"slug":240,"title":242},"wp-tagcat-community",{"current":241},"community","Community",{"_createdAt":226,"_id":244,"_rev":228,"_type":229,"_updatedAt":226,"slug":245,"title":247},"wp-tagcat-company",{"current":246},"company","Company",{"_createdAt":226,"_id":249,"_rev":228,"_type":229,"_updatedAt":226,"slug":250,"title":251},"wp-tagcat-survey",{"current":76},"Survey","How the 2019 Stack Overflow Developer Survey Came to Be (And Your Last Chance to Take it!)",[254,260,266,272],{"_id":255,"publishedAt":256,"slug":257,"sponsored":12,"title":259},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":258},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":261,"publishedAt":262,"slug":263,"sponsored":12,"title":265},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":264},"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":267,"publishedAt":268,"slug":269,"sponsored":12,"title":271},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":270},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"_id":273,"publishedAt":274,"slug":275,"sponsored":12,"title":277},"30b995f7-7cb9-4dd8-bf71-d0685940a32b","2026-06-19T14:00:00.000Z",{"_type":10,"current":276},"dispatches-from-o-reilly-from-capabilities-to-responsibilities","Dispatches from O'Reilly: From capabilities to responsibilities",{"data":279,"sourceMap":-1},{"count":280,"lastTimestamp":281},10,"2023-05-25T09:46:41Z"]