I don't think "we don't train on your data" means anything anymore
Between Samsung's engineers leaking their own source code into ChatGPT, DeepSeek leaving a database of a million chat logs sitting open with no login required, and Grok's share links somehow getting indexed on Google with 370k private conversations searchable, I've basically stopped believing "trust us" is a real answer from any frontier lab.
None of these were sketchy no-name startups either. These are the companies everyone's building on top of right now.
🚀 Launching in a week — here's my PH checklist. What am I missing?
Hey beautiful community
I'm new to the Product Hunt world. I've been building my product solo for the past 8 months and I'm launching this Thursday so I've been obsessively reading launch advice and building a checklist.
Here's what I've got so far, split into 3 phases. Please tear it apart and tell me what I'm missing
1 Pre-launch
Engage genuinely in the PH community (not just drop links)
Get the coming-soon page live so people can follow
Make sure supporters have accounts that aren't brand new (warm-up matters)
Warm up your audience outside PH too LinkedIn, X, communities
DM people ahead of time so launch day isn't a cold ask
Are You Dead Yet: The #1 app on China's Apple App Store
China's new top paid app doesn't help you find a ride, order food, or socialize with friends. It just asks you whether you're alive.
The app, which translates to "Are You Dead Yet?" the presence of the "yet" suggests the developer probably isn't on the Bryan Johnson "don't die" train...yet) requires you to log in daily and click a button to show you're alive. Miss two days in a row and the app will notify your emergency contact. That's it. That's the app.
Anyone else end up breaking their own initial startup rules just to survive?
When I first launched I swore I d keep things super minimal and never do heavy discounts or bloated features. A couple years in I catch myself making compromise after compromise just to keep numbers up. Partly because I was naive back then but partly because taking shortcuts was just easier. How do you tell if you re actually maturing as a founder or just losing your original vision?
Is “pick one thing and go deep” still good advice for indie hackers?
One of the most repeated pieces of startup advice is:
Pick one problem, build one product and spend years making it successful.
This makes sense when you are building a venture-backed company and trying to create one huge outcome. But I am not sure it is the best strategy for indie hackers. The alternative is what I call the many-donkeys thesis. Instead of betting your entire career on one product becoming a unicorn, you build a portfolio.
The bottleneck in software engineering isn't writing code anymore. It's trusting it.
The speed at which AI generates code has officially surpassed our capacity to review it. For decades, the bottleneck in software engineering was writing the code. Today, the bottleneck has shifted entirely to trusting that the code can run effectively in production and actually solve the business problem.
But let's be honest: humans never truly scaled code review anyway.
Throughout my career, I have observed developers approving PRs or MRs that contain critical bugs. When they do engage in the review process, they often focus on stylistic issues. Why does this happen? Because reviewers are overloaded with their own backlogs to manage, and often choose the path of least resistance by saying, "Looks good to me."
Now, we are trying to solve this by throwing AI at the problem!
The Missed Reality: Code Review Wasn't Built for the AI Era
Code review - whether conducted by a human or an LLM - was not designed for this era of autonomous coding. Code review does not actually verify whether the code accomplishes what was prompted, nor do they confirm that the code aligns with its intended specification or that an agent s "task completed" claim is deterministically true.
Even a well-conducted review adhering to the 5-axes best practices (correctness, architecture, security, readability, and performance) falls short. Rarely does a code review verify that the original acceptance criteria were met or that the AI agent didn't deviate from the scope just to finish the PR. LLMs notoriously defer hard, multi-step, or dependent tasks, which means that the intent itself has diverged. Furthermore, reviewers rarely verify that test coverage was maintained or check if the AI agent quietly weakened the tests along the way to secure a passing PR.
This leads to a critical question: Even if a human reviewer or an LLM could effectively manage all these new checks, can they realistically and deterministically do so given the massively increased speed of AI code generation?
The solution? We have to move from opinion-based review to evidence-based verification.
This means building guardrails (what I call the claim checker) that bind the original intent to deterministic evidence: ACs (intents) checks, the builds, the tests, the five-axis code review, the scans, the blast radius of the code change, the docs coverage, requirements are complete and don't contradict each other, and the monitoring coverage in the code.
AI can advise. But only evidence should decide whether to merge or not!
It s a shift we probably should have made years ago. But with agent loops writing code at machine speed, it is now the only way forward.
Fifteen blue buttons and the layer that never sees a selector
We asked a coding agent fifteen times to make one button blue on a page built to tempt it: Add to Cart and Checkout shared a class, a badge and the nav link shared the accent variable. Every run added an id-scoped rule. Checkout stayed green. Appending "Do not change anything else" changed one thing: the five runs with it wrote the hex inline where nine of the other ten had added two CSS variables. A path rule fencing off every file but the stylesheet never fired.
Real repositories look different. One benchmark pre-applied the fix to 200 issues and reopened them for five recent models in their vendors' harnesses. The right patch is empty; 35 to 65% of instances got an edit to executable code anyway, and in the authors' analysis of one model's failed traces, 87.1% had modified code unrelated to the issue. Task wording moved that figure a long way in both directions. Telling the agent to "edit the codebase" dragged one model's correct-abstention rate to 36.5%; reproduce first, then fix or abstain if nothing was wrong, lifted it to 88.5%. Their explanation: the agent acts on whatever it believes success means.
The harness side: switch on auto-accepted edits in both CLIs whose docs we read and the grant is the whole working directory. A path rule brings that down to files; one vendor's docs state that it applies to the built-in edit tools and recognized shell commands, and that a script opening a file itself is outside it. A selector inside a permitted file sits below every layer's resolution. Whether the blue landed on one button or on every primary button is decided by the sentence you typed and by whoever reads the diff.
When your agent overshoots, where does the boundary live in your setup today: the prompt, a rule file, a path rule, a sandbox, or the person reading the diff? Which of those has caught a change for you inside a file the agent was allowed to edit?
Product Hunt redesigned discussions with Reddit-style forums
AI made making things faster. Did it make reviewing more important?
AI has made it much faster to turn an idea into something you can actually look at and use.
But I m starting to wonder if that shifts the bottleneck rather than removing it.
When producing a new version takes less time, there are simply more versions to look at, more decisions to make, and more things that can move forward without much discussion.
From a product design perspective, that makes review feel more important, not less.
What are your favorite "fun" apps?
Yesterday @fmerian recommended Googly Eyes from @Sindre Sorhus, which I immediately downloaded! After enjoying the eyes following my cursor around for the day, that got me thinking - what other fun, goofy apps do you all have for your Mac, Chrome, or other devices that don't necessarily serve a purpose other than to bring joy and break the monotony? @Scroll Buddy is another one that comes to mind that I have saved in a collection.
We see productivity apps, AI-based software, open-source products, etc. all the time, but what about your saved products someone made after their 9-5 or on a weekend just to have fun and test their skills?