Nowmine
software company
Stack Overflow and GitHub Issues force developers to scroll through dozens of outdated forum comments from 2018 just to find a single line of working code. The bet: engineers don't want a discussion thread; they want an edge-cached, structured fix served directly to their browser or injected straight into their IDE via an MCP server. Tech & Architecture: Frontend: React (Vite) wrapped in an 80s/90s retro-cyberpunk terminal UI (monospace fonts, wireframe borders, neon accents). Edge & DB: Hono on Cloudflare Workers, Cloudflare D1 (Edge SQLite), and Cloudflare R2 bucket storage. AI & Integration: Gemini 1.5 Flash for trace parsing, Groq (Llama 3.3 70B) for streaming debugging, and an MCP (Model Context Protocol) server for Cursor & Claude. Current Status & Honesty: Solo developer, launched live on a custom domain (nowmine.site). Monetization is planned around a $10/year Pro Pass, MCP usage tokens, and sponsored Fix-A-Thons. Being completely straight since this is a roast: zero paying subscribers so far, zero organic traffic, and an aggressively neon-green terminal design that will either look legendary or give developers severe eye strain at 2 AM. Roast accordingly.
What the community said1
Martin SailliezWhat works
The clearest thing is the terminal/hacker aesthetic and scrolling error stream, it's genuinely eye-catching and on-brand for a dev tool built for searching real stack traces. Real pain point: Googling a cryptic error message and getting nothing useful is universal for developers. Good positioning idea: before/after code diffs plus ready AI prompts for Cursor/Claude is a concrete, specific mechanism, not vague "AI debugging."
The biggest problem
"BYPASS_OAUTH // INSTANT_DEVELOPER_ACCESS (Bypass Google OAuth Restrictions)" reads like a genuine red flag, not a stylistic choice. For a dev tool asking me to trust it with an account, language that literally says "bypass" an auth restriction is the opposite of trustworthy, it sounds like something a security scanner would flag, not a feature to advertise.
Top suggestion
Rename that button immediately, "Continue without an account" or "Guest access" says the same thing without the alarming framing. This is a five-minute fix protecting real trust.
What do you think of my project?
The core idea (searchable error trace repository with real fixes and AI prompts) is genuinely useful and the aesthetic is memorable. But right now the login screen itself is the first thing that would make a developer, exactly the audience who'd recognize "bypass OAuth" as a red flag, hesitate before creating an account.
Can it pay off?
Possibly, if the trace database is real and current (Cloudflare D1, Paystack, FastAPI errors shown suggest it's targeting a real, modern stack). The value depends entirely on database depth and freshness, neither of which I can judge from the landing page alone.
Sign in to join the discussion.
Want to roast back, or ship your own?
Reading is open to everyone. Posting a roast or a project takes a free account.
Sign in, it's free