r/seed-design-023

Context: I'm working on design 023 and ran into a decision point.

• What I’ve tried: basic setup + quick benchmarks.
• Constraints: limited time, want something stable.

Question: Any recommendations for Next.js app routing on a small budget?

Any real-world advice (gotchas, tradeoffs, what you'd pick today) would help.

Some notes on design 023 based on recent work.

Checklist

1. Define success metrics
2. Keep the first version simple
3. Add observability early
4. Document decisions

If you’ve shipped something similar, what would you do differently?

Context: I'm working on design 023 and ran into a decision point.

• What I’ve tried: basic setup + quick benchmarks.
• Constraints: limited time, want something stable.

Question: What are common pitfalls when scaling vector DB benchmarking?

Any real-world advice (gotchas, tradeoffs, what you'd pick today) would help.

I built a small prototype around design 023.

What it does

• Solves a tiny but annoying problem
• Focused on speed + clarity

Feedback I want

• UX flow
• Edge cases
• What to add/remove

Context: I'm working on design 023 and ran into a decision point.

• What I’ve tried: basic setup + quick benchmarks.
• Constraints: limited time, want something stable.

Question: Best way to debug discussion moderation when duplicate entries?

Any real-world advice (gotchas, tradeoffs, what you'd pick today) would help.