I m just a week away from launching my first product on Product Hunt. Super excited, super overwhelmed and last night, I found myself wondering: "How all this started?"

Truth is, I ve always been a restless soul (or as we say in Spanish, culo inquieto) once I ve learned everything in a role, I get bored. So I build. Not out of ambition, but out of a need to keep learning and growing.

I build a product mostly on my own, with agents doing a growing share of the mechanical work. This year my output went up and my days got worse, and it took me a while to see why.

Automation ate the typing. It did not touch the checking, and it multiplied the number of things waiting to be checked.

Then I found telemetry that matches: Faros AI looked at two years of workflow data from 22,000 developers across 4,000+ teams. Task throughput per developer up 33.7%. Median time a pull request sits in review up 441.5%. Daily PR contexts per developer up 67.4%.

For two years I forced myself to publish a brand new article every single Tuesday. I was exhausted. My organic traffic was completely flat despite having over a hundred posts on the site.

I looked at our analytics. Noticed that almost all our search traffic came from just five old articles. The rest of the content was sitting on page four of Google entirely ignored because it was outdated and lacked depth. I realized publishing volume was hurting my quality.

I stopped writing content for an entire month and focused only on those underperforming posts. I combined articles into massive guides updated old statistics from 2022 and added fresh screenshots from our current software version.

That simple cleanup effort boosted our site traffic by sixty percent in just forty days. Google clearly prefers an updated highly relevant page over a brand new post with zero domain authority.

I m currently working on a consumer mobile product aimed at a very specific blue-collar audience in the U.S.

One thing I m finding difficult is figuring out which acquisition channels are actually worth testing first.

For niche audiences like trucking, construction, logistics, field services, etc., do you think it s better to start with:

• short-form organic content

• niche communities

• creators/influencers

• referrals

• paid social

• search

Apple is now nudging people still on iOS 26 to move to iOS 27, and the 27.2 betas are already out. Every cycle like this makes me rethink the minimum OS question for a first release. I've found that supporting only the last two major versions keeps testing sane and lets you use newer APIs without workarounds. On Android it's messier, since a lot of real users sit on older devices for years, especially outside the US. If you're shipping a v1 on both platforms soon, where are you drawing the line? Do you check your target audience's device data first, or just pick a floor and adjust after launch?

Hey folks, I read 'Make' by Peter Levels years ago and found his process quite interesting:

1. Spending a week listing your personal problems,

2. Rank them, then look for solutions for the top three.

3. If nothing meets your needs, build it.

The beauty of this is that simply by doing the exercise, you end up meeting some of your needs by discovering something out there.

When I first started thinking about building a SaaS, support wasn't really on my list.

I was thinking about the obvious stuff:

• What features should I build?

• How should the UI look?

• How do I make it fast?

• How do I get the first users?

But the closer you get to actually putting a product in people's hands, the more you realize that users don't always experience your product the way you expect them to.

We once added a new permission to our extension and saw a massive drop in user count afterward. It could have been optional, but we made it required. That s something I d do differently now.

It got me thinking about what people check before giving an extension access to their browser. A useful feature might get your attention, but how much do permissions influence the decision?

Have you ever been ready to install an extension, then changed your mind? What put you off?

Writing code got cheap. Checking whether it did the thing did not, and the gap between those two is where I spent a whole day.

None of what follows was broken. Every line ran as written, raised no error, and reported success. That is the part worth talking about, because I think it is the real failure mode of this era and it does not look like a bug.

One. A refresh job reported one item refreshed. I checked the field that records when a price was last written and it had not moved. The counter incremented when the call returned rather than when a value was written, so it had been reporting success for as long as it had existed. It could not have reported anything else.

Two. A refresh path read one field name while the scraper was sending a different one. One word apart. When the price failed to parse, the missing field fell back to a default meaning the product does not exist, so live and in-stock listings were stamped as dead and pulled off a storefront. There was a comment directly above it explaining that a three strike threshold protects against exactly this. The threshold does nothing, because the validity check in the same function also requires a price and there was none. One event was enough. I found it by triggering it on my own site and taking two working products down.

I'll go first. A large HR platform sent out an automated AI-written email offering condolences on a prospect's coworker's death, and then tried to hook them into a demo.