ProductHunt is great! We just launched @Builduo and crossed 100 new users in the first 16 hours. I was prepared to see only a few sign ups, but it exceeded our expectations. Some X influencer posted us on their account and that got us a huge boost too!
I'm a solo founder. I make an LED light therapy mask, and I decided early that I wanted FDA 510(k) clearance rather than selling it as a generic beauty gadget. Many LED masks sold online aren't FDA-cleared at all, which tells you something about how painful the process is.
Twelve months. Roughly $140K. One person.
The single most expensive mistake I made was assuming a testing lab is a testing lab.
I picked one based on price and turnaround. Their reports looked professional. What I didn't check was whether their accreditation actually covered the specific standards my submission needed. It didn't. The data was unusable, and I had to run the testing again somewhere else months gone, and a large chunk of that $140K was just paying twice for the same tests.
Noticed a trend where letting agents work on whole features solo usually ends in a mess. They start tweaking low priority edge cases adding random bloat, or refactoring stuff that was working fine.
It seems like giving them complete freedom actually tanks the quality of the output.
What kind of rules or limits do you set so your coding tools don't end up going in circles?
Plan mode in coding agents sounds great on paper but actual implementation almost always deviates from the approved scope. Unwanted refactoring and premature "task finished" triggers are huge productivity killers.
Some developers use a second agent instance purely as a linter/checker, while others restrict execution to ultra strict prompt specs.
For those running agentic workflows daily: what setup has actually worked to keep implementation locked strictly to your initial plan
I make sure I get 8 hours, it's an luxury I know, but I found that I am the most happy at work, and most productive when I get my full 8 hours. Sacrificing sleep for me is just not worth it, bad for me, bad for people around me. What about you? How many hours do you sleep?
I went back through my DMs with early users recently. Messages from a year ago, when the product was rough and I was excited about everything.
Reading them was strange. The enthusiasm was real. Mine and theirs. They were actually rooting for me. They gave detailed feedback. They said "can't wait to see where this goes."
Almost all of them are gone now. Not angry. Just gone. No goodbye messages. Just silence.
I don't know what happened. Maybe the product didn't deliver. Maybe life got busy. Maybe they were just being nice in the beginning. I'll probably never know.
When your coding agent finishes a change and you ask it to look the change over, what is in the reviewer's window? If the answer is the whole session, the review is the author re-reading with its own notes in front of it: every file it opened, every dead end, and the moment it declared the change done. It knows why each line is there. A reviewer should not.
We wanted evidence that moving the review out of that window matters when the model stays the same. One small controlled study did exactly that: thirty artifacts with five planted errors each, one model, four review setups. The fresh window given nothing but the artifact caught the most, F1 28.6% against 24.6% for the full session and 40% of the critical errors against 29%, while a second pass inside the same session came last. Two agent vendors already build it that way: one CLI's guide puts it as a fresh context helping because the model "won't be biased toward code it just wrote", and the other vendor's team says one model does both jobs and was trained separately for each, with the reviewer running on the pull request.
Our own version reviews articles using a cold reviewer agent, handed that day's source material as ground truth. Each piece comes back with somewhere between one and twenty-three items we have to fix, usually four to six, and the hard ones were caught against the pasted sources.
If your agent reviews its own change, what does the reviewer get to see: the diff alone, the diff plus the task, or the whole transcript? And who has put two of those side by side on the same change?
I had a realization this morning that I can't shake.
Every single day, I apologize to someone. "Sorry, that feature isn't ready yet." "Sorry, the onboarding is confusing." "Sorry, I haven't replied to your email." "Sorry, the pricing page is broken on mobile."
I don't remember anyone telling me that 60% of building a product would be saying sorry to people who are kind enough to still care.
And here's the thing: I used to think "founder" meant vision, strategy, talking to users about the big picture. But most days, it's just managing a long list of small failures and trying to make sure the people who believed in you don't walk away before you fix them.