---
title: Every answer needs an expiry date
description: >-
  Stack Overflow made me wait eight weeks to speak, then deleted some of what I said. Meanwhile the
  answers that survived have been aging in public since 2013.
url: https://expiredqueues.com/answers-need-expiry-dates/
markdown: https://expiredqueues.com/answers-need-expiry-dates/index.md
date: '2026-07-05T10:00:00.000Z'
image: https://expiredqueues.com/images/og/answers-need-expiry-dates-ea9c531d.jpg
---

Retrospect posts stack-overflow

# Every answer needs an expiry date

5 July 2026 By Adrian Noel 3 min read

On this page

1. [Eight weeks to say anything](#eight-weeks-to-say-anything)
2. [Then some answers were deleted](#then-some-answers-were-deleted)
3. [The answers that survived](#the-answers-that-survived)
4. [What this blog does](#what-this-blog-does)
5. [What Stack Overflow could do](#what-stack-overflow-could-do)

I stopped using Stack Overflow years ago. My last answer there is dated May 2017.

This isn't a "the site is dying" post. It covers two things: what the site did to me, and what it still does to the sixty-four answers I left behind.

## Eight weeks to say anything

[I signed up on 26 July 2013](https://expiredqueues.com/six-weeks-in-2013/index.md). My first answer is dated 19 September.

I wasn't shy. A new account couldn't comment or do most other things. You earned your way in by upvoting other people and waiting. The site let you take part properly only after your reputation passed a threshold.

So my first weeks in the largest programming community in the world went to clicking arrows. Yucky weeks. I remember that feeling better than I remember any of the answers.

I understand why the gates exist. Spam is real, and nobody can moderate at that scale without automation. But filtering bad actors is one thing. Keeping a working developer with something useful to say in a waiting room for two months is another.

## Then some answers were deleted

Later, other people deleted a number of my answers. That was the community process working as designed. The questions had been closed, cleaned up or judged not to belong.

Some of that was probably fair. But I had written something, it had helped somebody, and then it was gone. I found out afterward.

So I stopped going back. I didn't write a rage-quit post.

## The answers that survived

Sixty-four answers are still there, and people still read them:

- The questions they sit on have around 992,000 views.
- [My top answer accounts for 478,000 of those](https://expiredqueues.com/most-read-thing-i-wrote/index.md).

The oldest are thirteen years old, and several are wrong now:

- Some name Bootstrap classes that no longer exist.
- One is [a modal hack that broke in Bootstrap 4](https://expiredqueues.com/answers-i-went-back-to-fix/index.md).
- One tells people to disable pinch-to-zoom on their phones.

Nothing on the page warns you. There's a date, in gray, at nine pixels, at the bottom. The accepted answer stays pinned at the top of the question. Its green tick means "this solved it in 2013." Readers take it to mean "this is the answer."

My reputation dropped by ten last year. I hadn't done anything. Nothing else happens to the account now.

## What this blog does

Every post here older than five years opens with a stamp:

- It's a big vermilion box with the post's age in years.
- Past five years, it tells you to read the post with the date in mind.
- At ten years and over, it says much of what the post describes has changed or disappeared. It says the post is kept as a record, not as advice.

I built the stamp because I have seventy-odd posts about PSD slicing and IE7 bugs. People still land on them from search. Letting those pages look current would be dishonest.

## What Stack Overflow could do

Stack Overflow could do the same thing tomorrow. It has the data: post age, last edit, and the version numbers in the tags. An accepted answer from 2013 on a `twitter-bootstrap` question could carry a banner the same size as the green tick.

I don't think reputation is the problem. I don't think the moderators are villains. [The interface treats a 2013 answer and a 2025 answer as the same kind of object](https://expiredqueues.com/books/the-design-of-everyday-things/index.md). It puts the older one on top because somebody clicked a tick thirteen years ago.

**Expired Queues is on YouTube.** Short videos on the same topics as this blog.

[Watch on YouTube](https://www.youtube.com/@expiredqueues)

[Previously I went back and fixed the commas](https://expiredqueues.com/answers-i-went-back-to-fix/index.md) [Next The most-read thing I ever wrote is a Stack Overflow answer](https://expiredqueues.com/most-read-thing-i-wrote/index.md)

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Every answer needs an expiry date",
  "description": "Stack Overflow made me wait eight weeks to speak, then deleted some of what I said. Meanwhile the answers that survived have been aging in public since 2013.",
  "datePublished": "2026-07-05T10:00:00.000Z",
  "dateModified": "2026-07-05T10:00:00.000Z",
  "author": {
    "@type": "Person",
    "name": "Adrian Noel",
    "url": "https://expiredqueues.com/about/"
  },
  "publisher": {
    "@type": "Person",
    "name": "Adrian Noel"
  },
  "mainEntityOfPage": "https://expiredqueues.com/answers-need-expiry-dates/",
  "keywords": "posts, stack-overflow, web-development, opinion",
  "articleSection": "Retrospect"
}
```
