# Stack Overflow: A Technical Deconstruction

DevFeed: [Stack Overflow: A Technical Deconstruction](<https://devfeed.tech/articles/stack-overflow-a-technical-deconstruction-21589.md>)

Original publisher: [Read original article](<https://nickcraver.com/blog/2016/02/03/stack-overflow-a-technical-deconstruction/>)

Published: 2016-02-03T00:00:00Z

Content type: opinion

Language: en

Sources: [Nick Craver](<https://devfeed.tech/sources/nick-craver.md>)

Topics: [Stack Overflow](<https://devfeed.tech/topics/stackoverflow.md>)

Tags: [blog](<https://devfeed.tech/tags/blog.md>), [developers](<https://devfeed.tech/tags/developers.md>), [technical](<https://devfeed.tech/tags/technical.md>)

## AI overview

Nick Craver introduces a planned series about Stack Overflow's technical practices and invites readers to suggest and prioritize future topics. He presents the series as an experiment in openness intended to share lessons and improve how the team works.

## Source excerpt

As new posts in the series appear, I'll add them here to serve as a master list: #1: Stack Overflow: The Architecture - 2016 Edition #2: Stack Overflow: The Hardware - 2016 Edition #3: Stack Overflow: How We Do Deployment - 2016 Edition #4: Stack Overflow: How We Do Monitoring - 2018 Edition #5: Stack Overflow: How We Do App Caching - 2019 Edition One of the reasons I love working at Stack Overflow is we're allowed encouraged to talk about almost anything out in the open. Except for things companies always keep private like financials and the nuclear launch codes, everything else is fair game. That's an awesome thing that we haven't taken advantage of on the technical side lately. I think it's time for an experiment in extreme openness. By sharing what we do (and I mean all of us), we better our world. Everyone that works at Stack shares at least one passion: improving life for all developers. Sharing how we do things is one of the best and biggest ways we can do that. It helps you. It helps me. It helps all of us. When I tell you how we do <something>, a few things happen: You might learn something cool you didn't know about. We might learn we're doing it wrong. We'll both find a better way, together...and we share that too. It helps eliminate the perception that "the big boys" always do it right. No, we screw up too. There's nothing to lose here and there's no reason to keep things to yourself unless you're afraid of being wrong. Good news: that's not a problem. We get it wrong all the time anyway, so I'm not really worried about that one. Failure is always an option. The best any of us can do is live, learn, move on, and do it better next time. Here's where I need your help I need you to tell me: what do you want to hear about? My intention is to get to a great many things, but it will take some time. What are people most interested in? How do I decide which topic to blog about next? The answer: I don't know and I can't decide. That's where you come in. Please, tel