@unclebigbay143 Would love your eyes on this one. fast markdown editor with live preview, mermaid and math, plus an mcp server so claude drops drafts right into your workspace https://t.co/9YdfBa897z
@justbyte_ Building edtr.md. problem: ai drafts die in chat tabs. it's a markdown editor your ai can write into directly (mcp), with diagrams, math and publish to web https://t.co/9YdfBa897z
@0xCharlota agree. ai made trying 10 directions cheap, but you still need a place to see all 10 side by side and pick one. code is a terrible place to compare options
@saaspentester lol. the boring checklist nobody vibes through: rls on, keys out of the frontend, rate limit auth. 10 min now or a very bad weekend later
@gldgab This is the right line. agent writes, you still review. "can it be undone" is the most underrated one on that list, most people find out after a bad migration
@CrowderSoup this is so true. every janky tool someone vibe coded is a feature request nobody filed. the hard part is the version that still works 6 months later, that's where engineering still matters
Everyone's racing to ship 10 apps a month with ai. nobody talks about what keeps app #1 alive
- a db backup you've actually restored once
- error tracking
- one test on the payment flow
- rate limits on auth
vibe coding is the fast part. this is the job
@Cipher_twt Best anti-slop tool is still reading your own output before you ship it. tools help, but if you can't tell what's slop, no linter will save you
@Lumitri_x "FOllOW" button is staying, that's branding now. Fr though, next step: ask it to explain the code back to you, you'll learn more from that than any tutorial
@Sayyidalijufri 200 days of showing up is the real flex. one idea: ask your best 5 users what they'd pay double for. that's usually where the next $1k is hiding
@sev_tinker yeah report it to cloudflare (abuse form) and file a DMCA with google too, that's what actually gets it deindexed. also set a canonical tag on your pages so google knows you're the original