Arko Dey

Have been a member on Product Hunt since 2017 but stopped participating for a while after leaving for two years. Forums are completely different now; forums are more like an actual hangout spot, not a discussion board attached to product launches. The classification of topics makes it much easier to find the relevant discussion, rather than scroll through the entire feed looking for one. One minor thing that I would love to have implemented on the platform is the ability to follow specific forums like p/vibecoding without following each single thread there because at the moment I am missing important posts or getting notifications all the time.

There were seventeen individual requests for keyboard shortcuts. I put them all in "nice to have" because there was no frequent use, at most, two times a day.

I shipped them last month in August. It took six hours and included a library and a help overlay. The daily sessions per user went from 2.1 to 3.8 within three weeks.

Something I wish I'd understood earlier about working with coding agents: there is no such thing as dispatching without a spec. There's only choosing who writes it.

When you send an agent a one-liner like "fix the login timeout", the unstated parts don't stay undecided. The model fills every blank with defaults from its training data the average project, the average convention, the average meaning of that sentence across every repo it has seen. Where your codebase matches the average, those fill-ins are invisible because they happen to be right. Where it doesn't, you get a diff that answers a question you never asked.

An intern who hits ambiguity tends to come ask. An agent mostly picks, and rarely flags the pick a constraint that never made it into the context might as well not exist.

So we stopped asking "spec or no spec" and started asking two questions before every dispatch. How long would a wrong guess stay invisible? And how far is this task from the average project the model trained on? Fast feedback plus mainstream shape: one line, go. Slow feedback plus weird shape: write the contract, and budget the writing as part of the build.