Connect with the Product Hunt community

I use a coding agent (omp) for most of my coding now, and I ship more than I used to. What I can't tell is whether I'm getting more done or just starting more things. It's so easy to kick off a new feature that I end up with a lot of half-finished work. I'm prone to that anyway, since I procrastinate and drop things too easily, and the agent makes it cheaper to jump to the next idea. Has your output actually gone up, or do you just feel busier? How do you tell the difference?

Gen Z took lying in bed all day and gave it a name that doesn't sound lazy. "Bed rotting." Doing everything from binge-watching to doomscrolling to staring at the ceiling. And the framing shifted from "being lazy" to "slowing down" and "self-care" .

I've been thinking about how this applies to building. There's a version of rest that's genuinely restorative. And there's a version where you're calling it "rest" but it's actually fear. Fear of the thing you should be doing. Fear of putting yourself out there. Fear of finding out the thing you built isn't good.

The hard part is knowing which one you're doing. From the inside, they feel identical.

How do you tell the difference between "I need this rest" and "I'm using this to avoid something"? Is there a signal you trust?

An enlightening conversation with my eldest cousin sister currently living abroad who used to work for Infosys 15 years ago:
Me: "Ya so Infosys is still doing mass hiring in Indian colleges, so is Wipro."
Her: "Oh okay, what's the package these days?"
Me: "3-6 LPA CTC."
Her: "What?? This is what WE were paid!"
My other cousin sister worked for Wipro. She said the exact same.
And then Narayana Murthy, Billionaire, Founder of Infosys, says that Indians should have a 72-hour work week, i.e, 12 hours for 6 days.
This is the current state of India's tech sector. Freshers, experienced developers, everyone is struggling to find a job in this market, having to settle for absolute outdated minimum wage stipends. The country's premier engineering institutes are an export sector for global tech companies contributing to the GDP of first world countries, all while said companies setup shop in Bengaluru, Pune, Hyderabad, Gurgaon and outsource majority of their work to cheap Indian labor.
But by all means, lets purchase AI tokens and further add to the problem.

I think having more tools to build with can make it harder to be honest with ourselves about an idea.

When something is difficult to build, the effort itself forces you to think carefully about whether it s worth pursuing. But when changes take minutes instead of days, it s tempting to keep experimenting just because you can.

Not every unfinished project needs another attempt, and not every rough idea needs to become a product.

I m curious whether the real challenge now is less about execution and more about choosing what deserves our attention in the first place.

We tried five different launch videos for our mobile app on social media. Some were lifestyle clips. Others were raw screen recordings of the core feature. The lifestyle videos got lots of views.. No one downloaded the app.

The raw screen recording that showed a user fixing a workflow error right away? It got over five hundred sign-ups in forty-eight hours. People on mobile don t wait for intros. They want to see what the product does fast.

Showing the product and its core use in the first three seconds changed everything. Our sign-ups went up. Our conversions improved.

What style of product demo video has brought the sign-ups, for your projects?

does this happen to anyone else?

you get an idea and it feels genius. you can't stop thinking about it, you start building right away. the first weeks are pure energy.

then somewhere along the way the doubts creep in. is this actually useful? would anyone pay for it? didn't someone
already do this better?

and the weird part is it gets worse the closer you get to finishing. right when there's not much left to do, I start seriously thinking about dropping it and moving on to the next shiny idea.

Ran a lifetime campaign a while back to get some initial cash and early testers.

It definitely helped with quick revenue but now those one time buyers take up almost all our daily support energy.

It feels like we spend way too much time fixing issues for non-paying users instead of focusing on building proper recurring revenue.

I've been wondering how other founders navigate this.

When you're building enterprise software, potential customers may expect security audits, SOC 2 reports, penetration testing, and extensive documentation before they're comfortable using your product.

But for a bootstrapped founder, those things can require significant money before you've earned your first dollar.

It feels like a difficult cycle: you need customers to fund security and compliance, but you need security and compliance to get customers.

I spent an entire afternoon trying to get an LLM to write API documentation for a payment gateway. The first three outputs were full of summaries and fake endpoint URLs that looked professional but were completely useless.

The breakthrough happened when I stopped asking for text and fed the model raw JSON payloads along with three specific error response codes. Giving it constraints forced it to write accurate reference guides instead of high-level marketing fluff.

Documentation turnaround time went from four hours down to twenty minutes per release. The secret is treating the model like a technical editor rather, than an open-ended creative writer.

How do you structure your input prompts to get technical output from generative AI models?

I ve been trying different tools to find competitors for my product, but most either show irrelevant results or miss similar products entirely.

Curious how other founders approach this. Do you rely on tools, Google searches, or manual research?

I m also wondering if there s a better way to solve this. Would love to hear your thoughts and recommendations.

I have been spending a bit of time testing out different calendar apps over the last few weeks to clean up my daily routine. It seems like every tool I try wants to be a full project management dashboard, a task manager, a habit tracker, and an AI scheduling assistant all at once.

Honestly, I usually just want a clean view of my day, quick event entry, and decent timezone handling. Half the time, all the extra features end up feeling like clutter rather than actual help. For those of you who use dedicated calendar tools, do you actually use all those extra features, or have you found a minimalist app that just sticks to doing the basics really well?

One thing I've learned while building software is that getting a feature to work and making it reliable are two different challenges.

A feature might work perfectly during testing but behave differently when real users interact with it.

For example:

• A form works, but doesn't handle unexpected input properly.

• An API responds correctly, but fails when an external service becomes unavailable.

• A dashboard displays accurate information, but doesn't distinguish between current and outdated data.

• An AI feature produces a convincing answer, but doesn't have enough context to support its conclusion.

The hardest thing to get right was getting people successfully through sign-up.

Initially I started with one time links, had a few successful sign ups and inbetween them would be a couple 'unauthenticated' emails. I would reach out via email to try find out why they didn't complete the process, but get no response. I eventually found out that some email providers burn the one time link when they scan the email.

I found that my automated coding assistants kept resetting my main environment template file every time I asked them to update dependencies. They acted like my config files were scratchpads erasing custom keys I needed for production. That was a headache.

The fix was simple: I set file-level permissions and added a clear exclusion list in the root instruction file. I made sure to tell the AI exactly which files were, off-limits. After that unintended changes stopped completely.

It saved me hours of debugging and made my local test runs consistent again. Now every time I use an agent the prompt includes a reminder to check file boundaries before running any script.

What method do you use to keep your coding tools from making unauthorized edits to sensitive system files?

Would love to know how many founders/makers here genuinely treat sunday as a day off versus just building at a slower pace instead of not building at all.

If you do take it off, what actually convinced you that was the right call.
And if you don't, is it because you genuinely want to be working, or because stopping feels like falling behind even when nothing's actually urgent.

I've been thinking about this since I watched a friend spin up a functional SaaS dashboard in a weekend using AI. It wasn't polished, but it worked. Two years ago that would have been a month of work.

On one hand, it feels like the barrier to entry has collapsed. On the other, the amount of noise on Product Hunt and Reddit has exploded. Every other launch is an AI wrapper or a "vibe-coded" tool.

If you're building now, does shipping something fast with AI still feel like an accomplishment, or has the goalpost moved to distribution and retention instead? Curious how others are calibrating their own sense of "done" when the tools make shipping so easy.

Working on a project that I will be submitting to the Muse platform for soon, but I'm curious to know if anyone has already gone down this route and what they've learned. I will report back when I learn more if others are curious.

Most startup advice is heavily biased toward people who succeeded which makes the quiet struggles feel way worse than they are.

I constantly find myself second guessing basic decisions like whether to push prices up, change direction, or just admit a feature flopped. The hardest part is knowing if staying the course is actual persistence or just stubbornness.

How do you personally decide when to keep tweaking an idea versus shutting it down and moving on?

I used to research competitors heavily before launching, then barely check them once I started building.

Most updates are easy to ignore. A pricing change, new integration, or shift in positioning can sometimes force a serious rethink.

Has a competitor ever made a move that changed what you built, priced, or removed? How did you decide whether to respond or stay focused on your own roadmap?

When you re building a product there s always another feature that seems worth adding. Fix one thing ship another get feedback then suddenly the next update is already in progress. I like the momentum but sometimes I wonder if constantly shipping makes it harder to step back and see what actually needs improving. How do you decide when to keep adding and when it s time to slow down and polish what you already have?

Notice this everywhere lol. Struggle always somehow resolves on a hopeful note, same length, same arc, every single time. Real struggle doesn't wrap up that clean in real time, ever.

Feels like "vulnerability" became a content format instead of an actual feeling.
People learned raw honesty performs well, so now it's structured like a post instead of just being said.

Not saying everyone's faking it.
Saying it's genuinely hard to tell who's actually mid-mess versus who figured out "Day 47, it's hard but i'm not quitting" is just a really good hook now.

Hey everyone,

I recently purchased the domain curetotal.com through GoDaddy - it's only about 25 days old under my ownership. But when I checked backlink data:

- Ahrefs shows ~1.1k backlinks

- Ubersuggest shows ~27 backlinks

I spent an hour writing a thread I was sure would spark discussion. Polished. Clear. A good question. Nobody replied.

|Then I posted something almost by accident. A messy observation about something I was stuck on. No structure. No point. Just a half-formed thought.

That one got replies. Real ones. People sharing their own experiences. A conversation.

I think the polished ones signal "I have this figured out, come admire my clarity." The messy ones signal "I'm actually stuck, help me think." People respond to the second one.

When I started I thought the hard part would be figuring out what to build. Turns out deciding what not to work on has been much harder. Every customer request feels important every new opportunity looks worth exploring and it s easy to keep changing direction when something isn t moving fast enough. How do you know when you re being flexible versus just losing focus?