It s so annoying when you feed an error to an agent it fixes one thing, breaks another, and then reverts right back to the first issue two turns later.
Once the chat gets flooded with raw logs it feels like it completely forgets the big picture and just starts guessing.
Do you just wipe the chat completely at that point or is there a prompt trick that actually gets it to stop and rethink?
The check is: count today s rows for this user, and if the count is under the limit, run the call and insert a row. That works for one request at a time. If a client sends 10 requests at once, all 10 can read count = 2 before any of them insert, so all 10 pass.
On serverless, this gets worse, because an in-memory counter doesn t help. Each request may run in a different instance with its own memory.
The fixes I m weighing, all in the database:
A unique constraint on (user, day, slot number). Each request claims the next slot, and a duplicate insert fails. It s simple, but I need to handle the retry.
An atomic counter. One SQL statement increments a per-user-per-day counter and returns the new value, and the request is rejected if it s over the limit. There s no gap between checking and counting.
An external store like Redis. It s fast, but it s one more service for a small stack.
I used to be a startup scout, and one of my sources of deal flow was actually the Product Hunt leaderboard. For fun, I m going to pick the top five products I find most interesting that launched in the last week from a scout POV. I ll try to veer away from the top products each day to keep things interesting.
@Check Supply (Send checks in the mail) --> Takes something that s been around for decades and feels like it s stuck in the Stone Age, and lowers the friction to accomplish the task at hand. Do young Gen Z ers even know how to write a check? I don't know, but I know many systems still rely on these. This makes sense.
@PickR (free e-sports prediction game) - Betting is in. I can bet on political events via @Polymarket. I can bet on sports. It s natural to assume betting on e-sports is going to be just as big (if not bigger). I see PickR building the stepping stones to unlock the next wave of betting, for better or for worse. (I don t even know if this is their intent, but this is where my brain went.)
Using supplier text on e-commerce pages is an easy shortcut early on but search engines eventually start treating all those pages as duplicate content. We saw a huge bump in search traffic after taking customer questions and real reviews to fill out missing details like dimensions and actual use cases.
Writing unique descriptions for every item manually takes forever if your catalog is huge. For those managing big stores what's your system for building helpful product pages without burning weeks on manual writing?
Two weeks ago, @byalexai discussed whether VCs are losing their appeal in the AI era. A few months ago, I personally noticed a lot of hate toward VCs and praise for bootstrapping on X.
It felt like VCs were being demonised: selective investors who take a big slice once a good opportunity appears, and then founders are expected to deliver top results while entrepreneurial freedom fades. That s how it was often framed.
365 days of non-stop innovation, exploration, and product excellence on Product Hunt! I open PH not for streaking but to see what's new in the tech world! That keeps me super motivated. I use PH as a platform to learn, inspire, and collaborate. Feel free to connect With me on Twitter and Linkedin Twitter : https://twitter.com/ranaumarsaleem
Linkedin : https://www.linkedin.com/in/rana...
We spent our first three months in beta completely free. The goal was simple: get people through the door, gather feedback, and build word-of-mouth. It worked. We were averaging about 150 new signups a week, and users were exploring every feature freely.
Last Tuesday, we finally introduced our basic subscription plan ($12/mo).
