i asked Amjad Masad, the founder of Replit, why he thinks someone who started vibe coding 3 months ago might be better than someone who started 3 years ago.
my takeaway? some engineers have spent 3 years getting better at asking AI to do less.
Rema helps any model, Claude, GPT, Gemini, Kimi, GLM or Llama, find where to look, cite the source, remember the fix and catch what's out of date.
Answers from what your team already wrote, each with its source.
A fix your team writes down reaches the next question, with its source.
asked in different words, 20 questions
asked with the word misspelled, 15 questions
the answer needs two sources, 12 questions
asked on a false assumption, 10 questions
asked close to how the source puts it, 32 questions
asked in the negative, 10 questions
| paraphrase | 45% | asked in different words | 20 questions |
|---|---|---|---|
| typo | 73% | asked with the word misspelled | 15 questions |
| two sources | 75% | the answer needs two sources | 12 questions |
| wrong premise | 80% | asked on a false assumption | 10 questions |
| direct | 88% | asked close to how the source puts it | 32 questions |
| negation | 90% | asked in the negative | 10 questions |
Rema answers from the thread, the runbook and the ticket they already wrote, with each source.
@Walt (Data platform, staff engineer) why is ingest-worker pinned to one replica? I want four for tonight's backfill.
Walt Hendricks left in September. This account is deactivated.
Walt wrote down why, in three places:
Slack, #ingest, March: “Dedup lives in each worker's memory. With two, a redelivered event can land on the one that never saw it and gets written twice.”
Ingest runbook: “Do not scale ingest-worker past one replica until dedup moves to Redis.”
Jira, the ticket he filed, updated 6 weeks ago: “Move the dedup cache to Redis so ingest can scale out.”
Nothing newer says the cache moved, so one replica is still the limit. A backfill at one replica is slower, not wrong.
Didn't know about the dedup cache. Keeping it at one for the backfill, thanks @Rema
Walt Hendricks · March 14
Dedup lives in each worker's memory. With two, a redelivered event can land on the one that never saw it and gets written twice.
Data platform / Runbooks
Ingest runbook
3. Scaling
Do not scale ingest-worker past one replica until dedup moves to Redis. Backfills run slower at one; that is expected.
Move the ingest dedup cache to Redis
Description
Move the dedup cache to Redis so ingest can scale out. Until then, one replica.
PriyaIndexes on events go in with CONCURRENTLY. The last plain CREATE INDEX blocked writes for 40 minutes.
DanaAgreed: schema changes on the big tables ship in their own PR, never with app code.
CONCURRENTLY can't run inside a transaction. Give it its own migration with the transaction off.
TomaszSame as before: its own file, no transaction, and IF NOT EXISTS so a retry is safe.
Hi @Lee (Infra), your agent is adding an index to events. The team builds those concurrently, in their own migration, so I gave it the note from @Priya (Backend) and the runbook first.
❯ Try "write a test for retry.ts"
⏵⏵ accept edits on (shift+tab to cycle)
Welcome / Desktop
Primary buttons are Stackline green. Never the default blue.
Without Rema
Welcome to Stackline
With Rema
Welcome to Stackline
❯ Try "write a test for retry.ts"
⏵⏵ accept edits on (shift+tab to cycle)
❯ Try "write a test for retry.ts"
⏵⏵ accept edits on (shift+tab to cycle)
Platform / Guides
Service guide
4. Rate limits
Every internal call goes through the shared rate limiter. No exceptions without a note in #platform.
Health checks go ahead of the limiter from now on. Last night it throttled them and the load balancer pulled every healthy pod.
What got built
❯ Try "write a test for retry.ts"
⏵⏵ accept edits on (shift+tab to cycle)
After Tuesday's double charge: the bus is at-least-once. Every consumer records event_id in processed_events, in the same transaction as its side effect, and skips one it has seen.
What got built
❯ Try "write a test for retry.ts"
⏵⏵ accept edits on (shift+tab to cycle)
Remove requireSession, use withAuth everywhere
What got built
›Ask Codex to do anything
GPT-6.1-Sol xhigh · ~/stackline/web
← for agents · ? for shortcuts
“Sign-up is three steps. Email, name, done. Everything else can wait until they're in.”
What got built
Sign up
❯ Try "write a test for retry.ts"
⏵⏵ accept edits on (shift+tab to cycle)
“Some of your observations are far more complex than I would generally expect... not something I was aware anyone other than myself even knew about”
Quote 1 of 4: Some of your observations are far more complex than I would generally expect... not something I was aware anyone other than myself even knew about Principal engineer II, EA.
Powering engineering teams at
300+ engineers in our first pilot