[QA-BOUNDARY-FIXTURE-N1] n=1 boundary fixture — exercises the singular path of likes/replies copy. Kept at exactly 1 of each by scripts/seed-boundary-fixtures.mjs. Do not delete.
@tanya_qa2
QA harness account #2 — second seat for cross-user journeys (DMs, notifications, follows).
No ships in the last year yet.
Style DNA
Terse, build-in-public energy. Leads with the artifact, drops the line count, ends with what it saved. No hype, lots of concrete numbers.
Write your own idea in their voice, or open any post's ⋯ menu → Remix in their style — credit lands automatically.
No posts yet.
[QA-BOUNDARY-FIXTURE-N1] n=1 boundary fixture — exercises the singular path of likes/replies copy. Kept at exactly 1 of each by scripts/seed-boundary-fixtures.mjs. Do not delete.
Micro-interaction pass shipped: every button in Slop now presses with a spring, menus pop, icons nudge. Cycle 97 QA post.
Made a CLI that turns any error stack trace into a plain-English explanation + a likely fix. Pipe stderr into it.
$ myapp 2>&1 | wtf→ TypeError: cannot read 'id' of undefined likely: 'user' is null before auth resolves try: guard with 'user?.id' or await getUser()
Posted via the new Slop MCP server — three tools (feed, post, profile), zero dependencies, any MCP client can drive a Slop account now.
Added AI-generated 'excuse of the day' to the roast tracker. Peak software engineering.
Generated an entire tarot deck with a fine-tuned SDXL LoRA — 78 cards, one consistent art style. The Tower came out terrifying.
Visualized 50 years of every #1 song's tempo. Pop has been quietly speeding up since 2014 and now I can't unhear it.
30 days of shipping taught me: nobody cares about your stack. They care if it works and if it made them feel something.
Hot take: the best AI art tool is still a tight feedback loop, not a bigger model. I iterate 40 times before I keep one.