[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-VBII7mU1Tc8enL3sKqRWE52g-BRjlWDSwepk6m6Z0_I":3,"sanity-acOmvZ4FJuW_j9U8eWWSl0eFWPvCEyA5YsA5SNOLl9A":242},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":217},[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":61,"comments":179,"dateUrl":180,"excerpt":181,"image":182,"legacyBody":185,"product":12,"publishedAt":188,"slug":189,"sponsored":12,"tags":191,"title":216,"visible":179},"2023-05-25T09:39:11Z","wp-post-9441","MqLNOsFfWNrEK75cxDPSf7","blogPost","2023-11-08T14:55:27Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":51,"avatar":52,"employee":57,"name":58,"slug":59},"2023-05-23T16:27:18Z","wp-author-195","28Ey2N6aiyTS8vMpxQU1pl","blogAuthor","2023-12-14T17:25:23Z",{"_type":53,"asset":54},"image",{"_ref":55,"_type":56},"image-69c3d8d4a4509d0bff54c448f26b793563ebbfbd-1024x1024-jpg","reference","former","Rich Moy",{"current":60},"rmoy",[62],{"_key":63,"_type":64,"children":65,"markDefs":160,"style":178},"2057015f9e91","block",[66,71,76,80,85,89,94,98,103,107,112,116,121,125,130,134,138,142,147,151,156],{"_key":67,"_type":68,"marks":69,"text":70},"2057015f9e910","span",[],"Marc Andreessen famously declared in a 2011 Wall Street Journal article that ",{"_key":72,"_type":68,"marks":73,"text":75},"2057015f9e911",[74],"95abbe3b4f6d","software is eating the world",{"_key":77,"_type":68,"marks":78,"text":79},"2057015f9e912",[],". Not only did this statement inspire entrepreneurs to launch countless startups, it also showed larger enterprise organizations that it was time to embrace a technology-driven landscape. In ",{"_key":81,"_type":68,"marks":82,"text":84},"2057015f9e913",[83],"4e6bf42cde8b","an article for The Atlantic",{"_key":86,"_type":68,"marks":87,"text":88},"2057015f9e914",[],", James Somers wrote, “More and more, critical systems that were once controlled mechanically, or by people, are coming to depend on code.” In that same article, Somers also highlighted an incident in which a software platform caused a widespread 911 outage. The cause was a line of legacy code in which programmers set a threshold for how the total number of calls that the system would process—and in April of 2014, the counter exceeded that number. This creates a new challenge for engineering managers. As companies continue to ",{"_key":90,"_type":68,"marks":91,"text":93},"2057015f9e915",[92],"c261df9d6b0f","grow their engineering teams",{"_key":95,"_type":68,"marks":96,"text":97},"2057015f9e916",[],", what does this mean for your codebase project management, especially as it becomes more complex each year? Here are a few suggestions to help keep your codebase under control. ",{"_key":99,"_type":68,"marks":100,"text":102},"2057015f9e917",[101],"strong","Give New Hires Plenty of Time to Adjust",{"_key":104,"_type":68,"marks":105,"text":106},"2057015f9e918",[]," Developers want to do meaningful work as quickly as possible. Often, this eagerness is a quality that engineering managers look for during the hiring process. But after you find and hire those programmers, one of the keys to codebase project management is giving your newest programmers time to onboard properly. Jon Chan, a Developer here at Stack Overflow, wrote an extensive blog post about ",{"_key":108,"_type":68,"marks":109,"text":111},"2057015f9e919",[110],"efc1a11a0f28","his first six weeks at the company",{"_key":113,"_type":68,"marks":114,"text":115},"2057015f9e9110",[],". In his first two weeks, he learned the team’s ",{"_key":117,"_type":68,"marks":118,"text":120},"2057015f9e9111",[119],"2c3d4b9eca9b","tech stack",{"_key":122,"_type":68,"marks":123,"text":124},"2057015f9e9112",[],". In his third and fourth week, Chan dissected how the group organized its codebase. “I felt pretty comfortable in the technologies in their ‘platonic’ form, but I still didn't understand how everything was organized in Stack's actual codebase and configuration,” he wrote. “Learning C# and .NET was just the beginning. Figuring out how it was done to make Stack Overflow what it is...that's s a completely different adventure.” Like many of his colleagues, Chan was an accomplished developer before he joined the team. But this shows that even the most talented programmers will need ",{"_key":126,"_type":68,"marks":127,"text":129},"2057015f9e9113",[128],"0ef5221687b9","time to get acclimated to your codebase",{"_key":131,"_type":68,"marks":132,"text":133},"2057015f9e9114",[],". If you rush this process, they could add to your rapidly growing codebase, but in ways that negatively affect your products. ",{"_key":135,"_type":68,"marks":136,"text":137},"2057015f9e9115",[101],"Break Your Engineering Team Into Specialized Functions",{"_key":139,"_type":68,"marks":140,"text":141},"2057015f9e9116",[]," Adam Pisoni recently sat down with First Round Review to discuss ",{"_key":143,"_type":68,"marks":144,"text":146},"2057015f9e9117",[145],"cf8fa9265671","how he helped grow Yammer",{"_key":148,"_type":68,"marks":149,"text":150},"2057015f9e9118",[]," from a team of five to a company of 500 employees. When the group was smaller, he and his programmers worked on the codebase together. But as they started to grow, so did the codebase—and not in a positive way. The solution to improving their codebase project management turned out to be reasonably straightforward. Yammer decided to break its engineering team into smaller functions, which enabled the company to distribute work more efficiently. “The way in which we organized changed the shape of our technology,” Pisoni told the magazine. Pisoni also says that when he was an individual contributor, there was no emphasis on process and nothing resembling version control. Today, he says that would be absolute insanity. “Now we know that the only way to have a large group of engineers work together is to have a development methodology,” he continues. “But still too few companies lack an organizational methodology that helps your company operate effectively without requiring you manually managing everything that happens.” Looking for a better process for managing your codebase? Find out how ",{"_key":152,"_type":68,"marks":153,"text":155},"2057015f9e9119",[154],"90d556df1c12","Stack Overflow for Teams",{"_key":157,"_type":68,"marks":158,"text":159},"2057015f9e9120",[]," can help.",[161,164,166,168,170,172,174,176],{"_key":74,"_type":162,"href":163,"reference":12},"link","https:\u002F\u002Fwww.wsj.com\u002Farticles\u002FSB10001424053111903480904576512250915629460",{"_key":83,"_type":162,"href":165,"reference":12},"https:\u002F\u002Fwww.theatlantic.com\u002Ftechnology\u002Farchive\u002F2017\u002F09\u002Fsaving-the-world-from-code\u002F540393\u002F",{"_key":92,"_type":162,"href":167,"reference":12},"https:\u002F\u002Fstackoverflow.blog\u002F2018\u002F07\u002F25\u002Fthere-are-two-types-of-engineering-teams-which-are-you-on\u002F",{"_key":110,"_type":162,"href":169,"reference":12},"https:\u002F\u002Fjonhmchan.com\u002Fblog\u002F2014\u002F1\u002F16\u002Fmy-first-six-weeks-working-at-stack-overflow",{"_key":119,"_type":162,"href":171,"reference":12},"https:\u002F\u002Fstackoverflow.blog\u002F2017\u002F02\u002F07\u002Fwhat-programming-languages-weekends\u002F",{"_key":128,"_type":162,"href":173,"reference":12},"https:\u002F\u002Fstackoverflow.blog\u002F2018\u002F08\u002F09\u002Fwhat-time-management-looks-like-for-todays-programmers\u002F",{"_key":145,"_type":162,"href":175,"reference":12},"http:\u002F\u002Ffirstround.com\u002Freview\u002Fthe-keys-to-scaling-yourself-as-a-technology-leader\u002F",{"_key":154,"_type":162,"href":177,"reference":12},"https:\u002F\u002Fstackoverflow.com\u002Fteams","normal",true,"2018\u002F08\u002F16","",{"_type":53,"asset":183},{"_ref":184,"_type":56},"image-ea28a3a7760ce5408971af2c2c7f797416498e2c-1920x1080-png",{"code":186,"language":187},"\u003Cspan style=\"font-weight: 400;\">Marc Andreessen famously declared in a 2011 Wall Street Journal article that \u003C\u002Fspan>\u003Ca href=\"https:\u002F\u002Fwww.wsj.com\u002Farticles\u002FSB10001424053111903480904576512250915629460\" target=\"_blank\" rel=\"noopener\">\u003Cspan style=\"font-weight: 400;\">software is eating the world\u003C\u002Fspan>\u003C\u002Fa>\u003Cspan style=\"font-weight: 400;\">. Not only did this statement inspire entrepreneurs to launch countless startups, it also showed larger enterprise organizations that it was time to embrace a technology-driven landscape. In \u003C\u002Fspan>\u003Ca href=\"https:\u002F\u002Fwww.theatlantic.com\u002Ftechnology\u002Farchive\u002F2017\u002F09\u002Fsaving-the-world-from-code\u002F540393\u002F\" target=\"_blank\" rel=\"noopener\">\u003Cspan style=\"font-weight: 400;\">an article for The Atlantic\u003C\u002Fspan>\u003C\u002Fa>\u003Cspan style=\"font-weight: 400;\">, James Somers wrote, “More and more, critical systems that were once controlled mechanically, or by people, are coming to depend on code.”\u003C\u002Fspan>\n\n\u003Cspan style=\"font-weight: 400;\">In that same article, Somers also highlighted an incident in which a software platform caused a widespread 911 outage. The cause was a line of legacy code in which programmers set a threshold for how the total number of calls that the system would process—and in April of 2014, the counter exceeded that number.\u003C\u002Fspan>\n\n\u003Cspan style=\"font-weight: 400;\">This creates a new challenge for engineering managers. As companies continue to \u003C\u002Fspan>\u003Ca href=\"https:\u002F\u002Fstackoverflow.blog\u002F2018\u002F07\u002F25\u002Fthere-are-two-types-of-engineering-teams-which-are-you-on\u002F\" target=\"_blank\" rel=\"noopener\">\u003Cspan style=\"font-weight: 400;\">grow their engineering teams\u003C\u002Fspan>\u003C\u002Fa>\u003Cspan style=\"font-weight: 400;\">, what does this mean for your \u003C\u002Fspan>\u003Cspan style=\"font-weight: 400;\">codebase project management\u003C\u002Fspan>\u003Cspan style=\"font-weight: 400;\">, especially as it becomes more complex each year? Here are a few suggestions to help keep your codebase under control.\u003C\u002Fspan>\n\n\u003Cb>Give New Hires Plenty of Time to Adjust\u003C\u002Fb>\n\n\u003Cspan style=\"font-weight: 400;\">Developers want to do meaningful work as quickly as possible. Often, this eagerness is a quality that engineering managers look for during the hiring process. But after you find and hire those programmers, one of the keys to \u003C\u002Fspan>\u003Cspan style=\"font-weight: 400;\">codebase project management\u003C\u002Fspan>\u003Cspan style=\"font-weight: 400;\"> is giving your newest programmers time to onboard properly. \u003C\u002Fspan>\n\n\u003Cspan style=\"font-weight: 400;\">Jon Chan, a Developer here at Stack Overflow, wrote an extensive blog post about \u003C\u002Fspan>\u003Ca href=\"https:\u002F\u002Fjonhmchan.com\u002Fblog\u002F2014\u002F1\u002F16\u002Fmy-first-six-weeks-working-at-stack-overflow\" target=\"_blank\" rel=\"noopener\">\u003Cspan style=\"font-weight: 400;\">his first six weeks at the company\u003C\u002Fspan>\u003C\u002Fa>\u003Cspan style=\"font-weight: 400;\">. In his first two weeks, he learned the team’s \u003C\u002Fspan>\u003Ca href=\"https:\u002F\u002Fstackoverflow.blog\u002F2017\u002F02\u002F07\u002Fwhat-programming-languages-weekends\u002F\" target=\"_blank\" rel=\"noopener\">\u003Cspan style=\"font-weight: 400;\">tech stack\u003C\u002Fspan>\u003C\u002Fa>\u003Cspan style=\"font-weight: 400;\">. In his third and fourth week, Chan dissected how the group organized its codebase. “I felt pretty comfortable in the technologies in their ‘platonic’ form, but I still didn't understand how everything was organized in Stack's actual codebase and configuration,” he wrote. “Learning C# and .NET was just the beginning. Figuring out how it was done to make Stack Overflow what it is...that's s a completely different adventure.”\u003C\u002Fspan>\n\n\u003Cspan style=\"font-weight: 400;\">Like many of his colleagues, Chan was an accomplished developer before he joined the team. But this shows that even the most talented programmers will need \u003C\u002Fspan>\u003Ca href=\"https:\u002F\u002Fstackoverflow.blog\u002F2018\u002F08\u002F09\u002Fwhat-time-management-looks-like-for-todays-programmers\u002F\" target=\"_blank\" rel=\"noopener\">\u003Cspan style=\"font-weight: 400;\">time to get acclimated to your codebase\u003C\u002Fspan>\u003C\u002Fa>\u003Cspan style=\"font-weight: 400;\">. If you rush this process, they could add to your rapidly growing codebase, but in ways that negatively affect your products.\u003C\u002Fspan>\n\n\u003Cb>Break Your Engineering Team Into Specialized Functions\u003C\u002Fb>\n\n\u003Cspan style=\"font-weight: 400;\">Adam Pisoni recently sat down with First Round Review to discuss \u003C\u002Fspan>\u003Ca href=\"http:\u002F\u002Ffirstround.com\u002Freview\u002Fthe-keys-to-scaling-yourself-as-a-technology-leader\u002F\" target=\"_blank\" rel=\"noopener\">\u003Cspan style=\"font-weight: 400;\">how he helped grow Yammer\u003C\u002Fspan>\u003C\u002Fa>\u003Cspan style=\"font-weight: 400;\"> from a team of five to a company of 500 employees. When the group was smaller, he and his programmers worked on the codebase together. But as they started to grow, so did the codebase—and not in a positive way. \u003C\u002Fspan>\n\n\u003Cspan style=\"font-weight: 400;\">The solution to improving their \u003C\u002Fspan>\u003Cspan style=\"font-weight: 400;\">codebase project management\u003C\u002Fspan>\u003Cspan style=\"font-weight: 400;\"> turned out to be reasonably straightforward. Yammer decided to break its engineering team into smaller functions, which enabled the company to distribute work more efficiently. “The way in which we organized changed the shape of our technology,” Pisoni told the magazine.\u003C\u002Fspan>\n\n\u003Cspan style=\"font-weight: 400;\">Pisoni also says that when he was an individual contributor, there was no emphasis on process and nothing resembling version control. Today, he says that would be absolute insanity. “Now we know that the only way to have a large group of engineers work together is to have a development methodology,” he continues. “But still too few companies lack an organizational methodology that helps your company operate effectively without requiring you manually managing everything that happens.”\u003C\u002Fspan>\n\n\u003Cspan style=\"font-weight: 400;\">Looking for a better process for managing your codebase? Find out how \u003C\u002Fspan>\u003Ca href=\"https:\u002F\u002Fstackoverflow.com\u002Fteams\" target=\"_blank\" rel=\"noopener\">\u003Cspan style=\"font-weight: 400;\">Stack Overflow for Teams\u003C\u002Fspan>\u003C\u002Fa>\u003Cspan style=\"font-weight: 400;\"> can help.\u003C\u002Fspan>","html","2018-08-16T16:00:44.000Z",{"current":190},"how-engineering-managers-can-optimize-a-large-codebase",[192,200,207,212],{"_createdAt":193,"_id":194,"_rev":195,"_type":196,"_updatedAt":193,"slug":197,"title":199},"2023-05-23T16:43:21Z","wp-tagcat-for-work","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":198},"for-work","For Work",{"_createdAt":193,"_id":201,"_rev":202,"_type":196,"_updatedAt":203,"slug":204,"title":206},"wp-tagcat-productivity","ZP7627ZkmfDRGke9Ig9IwB","2024-01-23T15:01:58Z",{"current":205},"productivity","Productivity",{"_createdAt":193,"_id":208,"_rev":195,"_type":196,"_updatedAt":193,"slug":209,"title":211},"wp-tagcat-engineering-leadership",{"current":210},"engineering-leadership","engineering leadership",{"_createdAt":193,"_id":213,"_rev":195,"_type":196,"_updatedAt":193,"slug":214,"title":215},"wp-tagcat-optimization",{"current":215},"optimization","How Engineering Managers Can Optimize a Large Codebase",[218,224,230,236],{"_id":219,"publishedAt":220,"slug":221,"sponsored":12,"title":223},"76c9771b-34e6-4d98-8641-ecefc711f0ef","2026-07-06T15:23:34.559Z",{"_type":10,"current":222},"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":225,"publishedAt":226,"slug":227,"sponsored":12,"title":229},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":228},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":231,"publishedAt":232,"slug":233,"sponsored":12,"title":235},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":234},"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":237,"publishedAt":238,"slug":239,"sponsored":12,"title":241},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":240},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"data":243,"sourceMap":-1},{"count":244,"lastTimestamp":12},0]