Someone has already
solved this
Threadline is a question and answer forum built around the archive. Ask once, get a checked answer, and leave something behind that still works for the next person in three years.
Open questions right now
Sorted by need rather than by recency — unanswered and bountied questions surface first.
- 46 votes3 answers4.1k viewsAccepted
Why does my migration lock the table only in production?
Same schema, same version, same row count in staging. In production the migration takes a full table lock for about forty seconds and I cannot reproduce it anywhere else.
databasesmigrationspostgres asked 2 hours ago - 88 votes7 answers12.4k views+150 bounty Accepted
Correct way to version an API when only one field changes type
A whole new version feels heavy for a single field going from string to integer, but I have consumers I cannot contact. What is the least disruptive route?
api-designversioning asked 6 hours ago - 31 votes0 answers890 views
Is there a reason to keep using a queue when the job takes 40ms?
We inherited a service where every job goes through a broker. Most now finish in well under a tenth of a second and the broker is the slowest part of the path.
architecturequeuesperformance asked Yesterday - 124 votes11 answers31.7k viewsAccepted
How do you test a function whose only job is to call three others?
Mocking all three feels like testing the mocks. Not testing it at all feels wrong. Where do people actually draw this line in practice?
testingmocking asked 2 days ago - 57 votes2 answers3.3k views+75 bounty
Rate limiting per user or per key when a user can hold many keys?
Per key is easy and gameable. Per user is fair and hard to implement across regions without a shared counter. Has anyone landed somewhere sensible?
rate-limitingdistributed-systems asked 3 days ago
Ask, answer, accept, repeat
Four steps, and the third is the one most forums skip.
- 01
Ask something answerable
The editor nudges you for what you tried and what constraint rules out the obvious fix. Questions with both get answered roughly three times faster.
median 18 min to first answer
- 02
Get answers, not opinions
Answers are votable and every claim can be challenged in comments. Wrong answers get corrected in public rather than quietly deleted.
94% of questions get one
- 03
Accept the one that worked
Only the person who asked can accept. It credits the answerer, closes the loop, and marks the thread as safe for the next reader.
71% acceptance rate
- 04
The archive does the rest
Accepted answers are indexed, linked from their tags and surfaced when a similar question is typed. Most value here is delivered to people who never post.
68% of traffic is search
The people whose answers keep getting accepted
Reputation here comes from answers marked correct by the person who asked, not from post volume.
| # | Member | Known for | Accepted | Reputation |
|---|---|---|---|---|
| 1 | IK Ines Kowalski 96 days active | Postgres, migrations | 412 | 48.2k |
| 2 | RD Rafael Duarte 41 days active | Distributed systems | 355 | 39.7k |
| 3 | MT Mei Tanaka | API design, versioning | 288 | 31.4k |
| 4 | OB Oliver Bennett | Testing strategy | 231 | 24.9k |
| 5 | SM Sofia Marchetti | Performance profiling | 187 | 19.6k |
Reputation resets its quarterly ranking but never its total. Accepted counts exclude self-answers.
A forum that ages well
The test of a Q&A site is whether a three-year-old thread is still worth reading.
“I found an accepted answer from 2029 that solved a lock contention issue exactly. The follow-up comments even flagged what changed in a later version.”
“The editor pushing me to say what I had already tried is mildly annoying and has halved the time it takes to get a useful reply.”
“Wrong answers get corrected instead of deleted, which means you can see the reasoning. That is worth more than a tidy thread.”
Before you post
The moderation and reputation rules people ask about most.
Almost always because it asks several things at once or has no answerable form. Closed questions are editable and reopen automatically once a moderator or three high-reputation members agree the edit fixed it.
You gain reputation when an answer is upvoted and considerably more when it is accepted by the asker. You cannot gain reputation from self-accepted answers, and reputation is never purchasable.
Bounties move reputation from your account to whoever answers a question that has gone quiet. They are the main tool for unsticking hard questions and they cannot be refunded once placed.
Not once it has an accepted answer. The archive is the point of the site, and deleting a solved thread takes value from everyone who would have found it later.
Only if you disclose it and have verified the answer yourself. Unverified generated answers are removed on sight, because an answer nobody checked is worse than no answer.
Ask the question you have been avoiding
Free to read and free to ask. Plans exist for teams that want a private space with the same mechanics.