[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"sanity-xeyAkCpTgscEVO3XsFpDJ_1jnOcUpbgkElDcJghYM2s":3,"sanity-frPFGmHdNGSGPOz0DPBuLdHhmkGLrbT-nuzcoVZoPPA":269},{"data":4,"sourceMap":-1},{"latestPodcast":5,"latestReleases":14,"post":39,"recent":244},[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":57,"comments":209,"dateUrl":210,"excerpt":211,"image":212,"legacyBody":216,"product":12,"publishedAt":219,"slug":220,"sponsored":12,"tags":222,"title":243,"visible":209},"2023-05-25T09:39:11Z","wp-post-9375","myT5Pq7GfgxKvTeIcgo72e","blogPost","2023-11-08T14:53:38Z",[46],{"_createdAt":47,"_id":48,"_rev":49,"_type":50,"_updatedAt":47,"avatar":51,"employee":53,"name":54,"slug":55},"2023-05-23T16:27:18Z","wp-author-200","9HpbCsT2tq0xwozQfkcuVr","blogAuthor",{"_type":52},"image","current","Derek Still",{"current":56},"dstill",[58],{"_key":59,"_type":60,"children":61,"markDefs":196,"style":208},"d15275943d33","block",[62,67,72,76,81,85,90,94,98,102,106,110,115,119,123,127,131,135,140,144,149,153,158,162,165,169,173,177,181,185,188,192],{"_key":63,"_type":64,"marks":65,"text":66},"d15275943d330","span",[],"Last week, I wrote about the ",{"_key":68,"_type":64,"marks":69,"text":71},"d15275943d331",[70],"873ec3a3aa2c","importance of building an internal developer community",{"_key":73,"_type":64,"marks":74,"text":75},"d15275943d332",[]," on the back of a talk at DeveloperWeek NYC about developers deserving better communication tools. I shared my thoughts with current customers and those evaluating Stack Overflow Enterprise, and a consistent theme in feedback that I received was that it comes down to the type of engineering culture a company has in place. This led me to dig back into my notes from other talks at DeveloperWeek. One that was particularly interesting and topical was ",{"_key":77,"_type":64,"marks":78,"text":80},"d15275943d333",[79],"ca0f584476ba","Hamid Shojaee’s",{"_key":82,"_type":64,"marks":83,"text":84},"d15275943d334",[]," talk about common traits that successful Agile development teams possess. He broke it down by rightfully arguing that there are two types of development teams: those that say, ",{"_key":86,"_type":64,"marks":87,"text":89},"d15275943d335",[88],"em","“We can do anything!",{"_key":91,"_type":64,"marks":92,"text":93},"d15275943d336",[],"” and those that say “",{"_key":95,"_type":64,"marks":96,"text":97},"d15275943d337",[88],"Well, we’ve never done that before…",{"_key":99,"_type":64,"marks":100,"text":101},"d15275943d338",[],"”. After spending the last five years talking to CTOs, CIOs, and engineering leaders focused on transforming their culture, the “",{"_key":103,"_type":64,"marks":104,"text":105},"d15275943d339",[88],"We can do anything!",{"_key":107,"_type":64,"marks":108,"text":109},"d15275943d3310",[],"” teams have similar characteristics: ",{"_key":111,"_type":64,"marks":112,"text":114},"d15275943d3311",[113],"strong","They have a “do” instead of “ask” mentality",{"_key":116,"_type":64,"marks":117,"text":118},"d15275943d3312",[]," They are consciously and actively putting practices in place to fix problems within. Engineering teams that have a “do” mentality are generally smart and eager to get things done instead of asking others to handle the job for them. ",{"_key":120,"_type":64,"marks":121,"text":122},"d15275943d3313",[113],"They are willing to fail",{"_key":124,"_type":64,"marks":125,"text":126},"d15275943d3314",[]," Engineers on these teams take a calculated approach to risk but, most importantly, they are willing to fail and will stick their neck out to make a change in their organization when needed. As doers, they look at the positive and transformational change that they can make in a project/product or in their team. ",{"_key":128,"_type":64,"marks":129,"text":130},"d15275943d3315",[113],"They're collaborative",{"_key":132,"_type":64,"marks":133,"text":134},"d15275943d3316",[]," We’ve written a lot about how ",{"_key":136,"_type":64,"marks":137,"text":139},"d15275943d3317",[138],"b61e99fe0b64","pair programming can make for a better programmer",{"_key":141,"_type":64,"marks":142,"text":143},"d15275943d3318",[],", ",{"_key":145,"_type":64,"marks":146,"text":148},"d15275943d3319",[147],"8986974ee7d8","how engineering managers can improve communication between technical and non-technical teams",{"_key":150,"_type":64,"marks":151,"text":152},"d15275943d3320",[]," and ",{"_key":154,"_type":64,"marks":155,"text":157},"d15275943d3321",[156],"555427cdecb5","how engineering managers can effectively manage a remote team of developers",{"_key":159,"_type":64,"marks":160,"text":161},"d15275943d3322",[],". The key theme? Collaboration! Engineers on the “",{"_key":163,"_type":64,"marks":164,"text":105},"d15275943d3323",[88],{"_key":166,"_type":64,"marks":167,"text":168},"d15275943d3324",[],"” teams are consistently communicating & collaborating with one another in an effort to learn from their colleagues. ",{"_key":170,"_type":64,"marks":171,"text":172},"d15275943d3325",[113],"They're metrics-driven",{"_key":174,"_type":64,"marks":175,"text":176},"d15275943d3326",[]," When it comes to improving the collaboration between teams, for instance, engineering leaders that believe they can do anything don’t just rely on the accepted fact that it needs to be improved. Rather, they proactively poll their engineering teams about how long it takes them to get a peer-validated, objectively accurate answer to a question, how many tools they need to go through to find that answer, the number of steps involved, etc. ",{"_key":178,"_type":64,"marks":179,"text":180},"d15275943d3327",[113],"They prefer fewer, more useful tools",{"_key":182,"_type":64,"marks":183,"text":184},"d15275943d3328",[]," Engineers are most productive when they’re in a distraction-free flow state and writing high-quality code. Companies that give their engineering teams every tool under the sun are actually preventing them from getting into this state. “",{"_key":186,"_type":64,"marks":187,"text":105},"d15275943d3329",[88],{"_key":189,"_type":64,"marks":190,"text":191},"d15275943d3330",[],"” teams understand that there are only a few mission-critical tools that their engineers need to get their jobs done; all the rest are a hindrance to individual and team productivity. ",{"_key":193,"_type":64,"marks":194,"text":195},"d15275943d3331",[88],"There’s a clear cultural divide between the two types of teams: what type of team are you a part of?",[197,200,202,204,206],{"_key":70,"_type":198,"href":199,"reference":12},"link","https://stackoverflow.blog/2018/06/25/the-importance-of-building-an-internal-developer-community/",{"_key":79,"_type":198,"href":201,"reference":12},"https://twitter.com/hamids",{"_key":138,"_type":198,"href":203,"reference":12},"https://stackoverflow.blog/?s=pair+programming",{"_key":147,"_type":198,"href":205,"reference":12},"https://stackoverflow.blog/2018/06/20/how-engineering-managers-can-improve-communication-between-technical-and-non-technical-teams/",{"_key":156,"_type":198,"href":207,"reference":12},"https://www.stackoverflowbusiness.com/blog/how-engineering-managers-can-effectively-manage-a-remote-team-of-developers","normal",true,"2018/07/25","",{"_type":52,"asset":213},{"_ref":214,"_type":215},"image-c30acca2b7105e933680d07c7bc4cb556d613b87-1920x1080-jpg","reference",{"code":217,"language":218},"\u003Cspan style=\"font-weight: 400;\">Last week, I wrote about the \u003C/span>\u003Ca href=\"https://stackoverflow.blog/2018/06/25/the-importance-of-building-an-internal-developer-community/\">\u003Cspan style=\"font-weight: 400;\">importance of building an internal developer community\u003C/span>\u003C/a>\u003Cspan style=\"font-weight: 400;\"> on the back of a talk at DeveloperWeek NYC about developers deserving better communication tools.  I shared my thoughts with current customers and those evaluating Stack Overflow Enterprise, and a consistent theme in feedback that I received was that it comes down to the type of engineering culture a company has in place.\u003C/span>\n\n\u003Cspan style=\"font-weight: 400;\">This led me to dig back into my notes from other talks at DeveloperWeek. One that was particularly interesting and topical was \u003C/span>\u003Ca href=\"https://twitter.com/hamids\">\u003Cspan style=\"font-weight: 400;\">Hamid Shojaee’s\u003C/span>\u003C/a>\u003Cspan style=\"font-weight: 400;\"> talk about common traits that successful Agile development teams possess. He broke it down by rightfully arguing that there are two types of development teams: those that say, \u003C/span>\u003Ci>\u003Cspan style=\"font-weight: 400;\">“We can do anything!\u003C/span>\u003C/i>\u003Cspan style=\"font-weight: 400;\">” and those that say “\u003C/span>\u003Ci>\u003Cspan style=\"font-weight: 400;\">Well, we’ve never done that before…\u003C/span>\u003C/i>\u003Cspan style=\"font-weight: 400;\">”.\u003C/span>\n\n\u003Cspan style=\"font-weight: 400;\">After spending the last five years talking to CTOs, CIOs, and engineering leaders focused on transforming their culture, the “\u003C/span>\u003Ci>\u003Cspan style=\"font-weight: 400;\">We can do anything!\u003C/span>\u003C/i>\u003Cspan style=\"font-weight: 400;\">” teams have similar characteristics:\u003C/span>\n\n\u003Cspan style=\"font-weight: 400;\">\u003Cstrong>They have a “do” instead of “ask” mentality\u003C/strong>\u003C/span>\n\n\u003Cspan style=\"font-weight: 400;\"> They are consciously and actively putting practices in place to fix problems within. Engineering teams that have a “do” mentality are generally smart and eager to get things done instead of asking others to handle the job for them.\u003C/span>\n\n\u003Cstrong>They are willing to fail\u003C/strong>\n\n\u003Cspan style=\"font-weight: 400;\">Engineers on these teams take a calculated approach to risk but, most importantly, they are willing to fail and will stick their neck out to make a change in their organization when needed. As doers, they look at the positive and transformational change that they can make in a project/product or in their team.\u003C/span>\n\n\u003Cstrong>They're collaborative\u003C/strong>\n\n\u003Cspan style=\"font-weight: 400;\">We’ve written a lot about how \u003C/span>\u003Ca href=\"https://stackoverflow.blog/?s=pair+programming\">\u003Cspan style=\"font-weight: 400;\">pair programming can make for a better programmer\u003C/span>\u003C/a>\u003Cspan style=\"font-weight: 400;\">, \u003C/span>\u003Ca href=\"https://stackoverflow.blog/2018/06/20/how-engineering-managers-can-improve-communication-between-technical-and-non-technical-teams/\">\u003Cspan style=\"font-weight: 400;\">how engineering managers can improve communication between technical and non-technical teams\u003C/span>\u003C/a>\u003Cspan style=\"font-weight: 400;\"> and \u003C/span>\u003Ca href=\"https://www.stackoverflowbusiness.com/blog/how-engineering-managers-can-effectively-manage-a-remote-team-of-developers\">\u003Cspan style=\"font-weight: 400;\">how engineering managers can effectively manage a remote team of developers\u003C/span>\u003C/a>\u003Cspan style=\"font-weight: 400;\">. The key theme? Collaboration! Engineers on the “\u003C/span>\u003Ci>\u003Cspan style=\"font-weight: 400;\">We can do anything!\u003C/span>\u003C/i>\u003Cspan style=\"font-weight: 400;\">” teams are consistently communicating & collaborating with one another in an effort to learn from their colleagues.\u003C/span>\n\n\u003Cstrong>They're metrics-driven\u003C/strong>\n\n\u003Cspan style=\"font-weight: 400;\">When it comes to improving the collaboration between teams, for instance, engineering leaders that believe they can do anything don’t just rely on the accepted fact that it needs to be improved. Rather, they proactively poll their engineering teams about how long it takes them to get a peer-validated, objectively accurate answer to a question, how many tools they need to go through to find that answer, the number of steps involved, etc.\u003C/span>\n\n\u003Cstrong>They prefer fewer, more useful tools\u003C/strong>\n\n\u003Cspan style=\"font-weight: 400;\">Engineers are most productive when they’re in a distraction-free flow state and writing high-quality code. Companies that give their engineering teams every tool under the sun are actually preventing them from getting into this state. “\u003C/span>\u003Ci>\u003Cspan style=\"font-weight: 400;\">We can do anything!\u003C/span>\u003C/i>\u003Cspan style=\"font-weight: 400;\">” teams understand that there are only a few mission-critical tools that their engineers need to get their jobs done; all the rest are a hindrance to individual and team productivity.\u003C/span>\n\n\u003Cem>\u003Cspan style=\"font-weight: 400;\">There’s a clear cultural divide between the two types of teams: what type of team are you a part of?\u003C/span>\u003C/em>","html","2018-07-25T16:00:48.000Z",{"current":221},"there-are-two-types-of-engineering-teams-which-are-you-on",[223,231,238],{"_createdAt":224,"_id":225,"_rev":226,"_type":227,"_updatedAt":224,"slug":228,"title":230},"2023-05-23T16:43:21Z","wp-tagcat-for-work","9HpbCsT2tq0xwozQfkc4ih","blogTag",{"current":229},"for-work","For Work",{"_createdAt":224,"_id":232,"_rev":233,"_type":227,"_updatedAt":234,"slug":235,"title":237},"wp-tagcat-productivity","ZP7627ZkmfDRGke9Ig9IwB","2024-01-23T15:01:58Z",{"current":236},"productivity","Productivity",{"_createdAt":224,"_id":239,"_rev":226,"_type":227,"_updatedAt":224,"slug":240,"title":242},"wp-tagcat-engineering-leadership",{"current":241},"engineering-leadership","engineering leadership","There are Two Types of Engineering Teams. Which Are You On?",[245,251,257,263],{"_id":246,"publishedAt":247,"slug":248,"sponsored":12,"title":250},"28e560af-f0aa-4d46-bd90-f435ad604aa7","2026-06-26T14:00:27.102Z",{"_type":10,"current":249},"paging-charity-how-can-engineering-leaders-avoid-becoming-bond-villains","Paging Charity! How can engineering leaders avoid becoming Bond villains?",{"_id":252,"publishedAt":253,"slug":254,"sponsored":12,"title":256},"4b22c2a3-3779-4966-93eb-5230391dbdce","2026-06-23T14:08:58.595Z",{"_type":10,"current":255},"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":258,"publishedAt":259,"slug":260,"sponsored":12,"title":262},"5cf362e1-fe7b-45af-b69c-914731c6a052","2026-06-23T14:00:00.000Z",{"_type":10,"current":261},"the-2026-developer-survey-is-now-open-for-human-developers-only","The 2026 Developer Survey is now open (for human developers only)!",{"_id":264,"publishedAt":265,"slug":266,"sponsored":12,"title":268},"30b995f7-7cb9-4dd8-bf71-d0685940a32b","2026-06-19T14:00:00.000Z",{"_type":10,"current":267},"dispatches-from-o-reilly-from-capabilities-to-responsibilities","Dispatches from O'Reilly: From capabilities to responsibilities",{"data":270,"sourceMap":-1},{"count":271,"lastTimestamp":12},0]