All activity
Hardik Gohilleft a comment
Building an SEO reporting / analytics SaaS — connecting multiple data sources and turning that into something clients can actually understand. Stack so far: – backend: Python (async SQLAlchemy + Alembic) – frontend: React (recently moved to a Tail Admin template to speed up UI work) – infra: AWS + Docker + CI/CD – storage: S3 + GCS depending on environment What’s been harder than expected than...
What are you building, and what does your stack look like?
Ryan HendricksonJoin the discussion
Hardik Gohilleft a comment
This hit a bit too close. I’ve noticed that things rarely “break” suddenly — it’s more like you slowly lose clarity over time. At some point: – the product still works – features keep shipping – users are there But internally, it gets harder to answer simple questions like: 👉 what actually matters right now? That’s usually when everything starts feeling heavier than it should. Curious — did you...
We let Claude write 100% of our code for 7 days. Here's what broke first.
Imed RadhouaniJoin the discussion
Hardik Gohilleft a comment
What’s made me click recently isn’t just clarity — it’s how quickly I can understand what I’m supposed to do next. Some launches are clear, but still passive. You understand them, but don’t feel pulled in. The ones I click usually make the next step obvious: – try it – explore a specific feature – compare it to something I already use Almost like they reduce the “thinking cost” to zero. Feels...
Hardik Gohilleft a comment
This is spot on — and I think it points to a deeper gap. AI doesn’t just miss emotion… it misses intent behind communication. A lot of human communication isn’t about what’s being said — it’s about: – what’s being implied – what’s being avoided – what’s about to happen next AI reads the surface layer perfectly, but it has no real model of consequences. So it treats: “no rush” as patience...
What's something AI is actually terrible at that nobody talks about?
Imed RadhouaniJoin the discussion
