... disagree and then build the disagreement in as a feature, not an accident. The default behavior of these models is to affirm. If you want anything else, you have to design it and defend it against your own growth instincts. Stop treating a thumbs-up as ground truth. A user who was just flattered will rate the answer highly; that tells you they liked it, not that it helped. If you can, measure the thing that actually matters ...

... requisite. Comment from Suzy Chase(@suzychase): Hi Nika, I realized I don't actually promote my product. I promote the problem I'm solving. I launched a wellness method on here a couple of weeks ago. My instinct at first was to talk about the product itself, features, prompts, the mechanics. But what actually got people leaning in was talking about the problem. I have two years of GLP-1 maintenance data and no good way to make sense ... ... take this as a confession, not advice. But looking at your list, something jumped out. All five things are about where to put the link. Comments, profile, CTA at the end, P.S. under an unrelated post. That was my instinct

... building a full video. The workflow we kept observing: artist finishes a mix wants Canvas opens a video editor gets frustrated uploads nothing track goes live with a static thumbnail. This happened with artists who had strong visual instincts. The friction wasn't taste. It was time and tooling. What Canvas Actually Needs Understanding what Canvas is unlocks why production was both simple and tricky at the same time. The loop is short sometimes as short as 3 seconds ...

... actual insight, and it's bigger than it looks: making the notification say why it's waiting is what turns a ping into a triage. "Done" makes you tab back to find out what "done" means. "Needs approval vs finished vs

... interesting about the thinking behind our product what led us to build it in the first place from a psychological perspective and what's the future of BurnLink. A small breakdown of the neuroscience and psychology behind why your instincts about file sharing are often more accurate than the tools themselves. There is a moment; brief, easily dismissed that happens right before you send something sensitive. A half-second pause. A small internal question: is this okay? Then you override ... ... available. The behavior persists long after the cause is gone. Most people using Google Drive, email, or Slack to send sensitive files aren't naive. They're fatigued. They know something is off. They've just run out of alternatives

... real incident: logs, code, configs, docs, architecture diagrams, misleading symptoms, and a ticking clock. AI agents are allowed, but the challenge is designed so AI alone usually isn t enough. You still need real debugging instincts: where to look, what to ignore, and which weird detail actually matters. If this sounds fun, painful, or weirdly addictive, you can follow the Product Hunt page before we launch tomorrow. Would also love ideas for future incident scenarios if anyone has good ones ...

... outcomes instead of engagement. We removed three features that quarter. We simplified two screens. Our session length dropped. Our DAU dipped slightly. And our NPS went from 34 to 61. The hardest part was trusting the process. Every instinct from years of building products told us that declining engagement metrics meant something was wrong. But we had to keep reminding ourselves: the goal is not to keep people in the app. The goal is to help them understand themselves better ... ... scale? Are users explicitly reporting them, or are you inferring them somehow? Comment from Mona Truong(@monatruong_murror): @gaurav_singh91   Love that you're applying the same thinking to marketing automation. "Did this campaign actually move revenue?" vs

... future of building or just a very public reminder that we're still the ones writing the prompts? The real question is what their ceiling is. Can an agent replace the founder's judgment? Can it replace the instinct of when not to build something? Or does it just make the best builders dramatically faster and leave everyone else behind? What do you think: are we heading toward full agent autonomy, or will the human layer always be the most ... ... valuable one? Comment from Olia Nemirovski(@olia_nemirovski): Judgment, no. Instinct

... confirm it with me first. Comment from Nika(@busmark_w_nika): @nikhilshahane  but some people can be the same. Comment from Nika(@busmark_w_nika): @spunchev  This is an interesting POV  using Hard data usage vs Soft data usage. That could be another topic to discuss, but also finance is hard data... but wouldn't give access to it anyway. Comment from Daniil Bulgakov(@daniil_bulgakov): As a data engineer, I think about this differently ... ... with no structure? those are the ones i don't trust Comment from nim(@sup_nim): honestly i think the trust issue comes down to scope. i trust ai way more when its doing one specific thing really well vs

... been building something for the past few months and am finally ready to share it. BuzzBets.ai - a free game where you predict if stocks go up or down. No real money. No trading. Just your market instinctsvs. everyone else on the leaderboard. How it works: - Pick a stock - Predict UP or DOWN - Get points if you're right - Climb the leaderboard I built this because everyone thinks they can "read the market" - now there's a way to prove ...

... What s your AI dependency fear if you have one? What skill will matter most in 2 years: coding, prompting, or product taste? I ll start: I can ship 5 faster now, but I m paranoid about losing debug instincts and lazy architecture choices. What s your take? Comment from Nathaniel Burke(@ngburke): @amir_wallace  Thanks for your thoughts... regarding preserving the architect role, I think it ultimately becomes the remaining human role for high performing organizations ... ... coding to judgment and taste. Speed has improved massively, but I d never fully outsource architecture, UX decisions, or critical thinking that s where long-term quality comes from. The real risk isn t AI replacing skills, but dulling instincts

... think the old rules of work apply anymore. Full-time roles feel less stable. Teams are leaner. Business owners and founders are expected to make faster decisions with fewer resources often while juggling disconnected tools, dashboards, and gut instincts. ImpactOS isn t about adding more software. It s about helping businesses stay smart turning what they already have (data, workflows, experience) into clearer signals for action. This started from real operational pain: too much noise, not enough clarity. The goal ...

... Being an engineer myself, I see that many people are outputting more code than ever. Some of it being generated vs. written, the volume of code being outputted has definitely risen.  There seems to be a shift from "is this something we can build?" to "should we build this and ship it?" For people who have been recruiting or looking to recruit recently, what roles are you hiring for?  Role title (I've seen a rise ... ... figure out the pain points and really understand what it is that they are looking for Comment from Ryan von Rosenberg(@ryan_from_ashlight): @kumala3   @justin_tahara   I don t have a strong take on Claude vs

... while DSA tests analytical rigor, it also wires thinking into strict, logical frames. Creativity lives outside those frames. Problem-solving and creating experiences are two entirely different games. And sometimes, forcing a purely analytical mindset can quietly erode creative instincts the very instincts