On many accounts in forum i can see badge with relation to their product. I would to configure my account in same way. Product was launched moth ago, i am assigned as maker, but still i only see my account name. How can i change it?
We always talk about the excitement of launch day, but the days right after can be a mental roller coaster especially when traffic slows down and user feedback trickles in slowly.
What s your personal ritual or strategy to stay disciplined and keep iterating when the initial launch hype fades?
P.S. Currently resisting the urge to refresh my analytics page for the 47th time today. Send help (or advice).
We pull job posts from a few dozen boards and company career pages, and each one is keyed on its source plus that source's own id. That works inside one source and does nothing across them: the same opening can arrive from the company's own page, an aggregator and a recruiter repost, each with a slightly different title and location line. Matching on company plus title looks obvious until you meet one company with two genuinely separate Backend Developer openings in two cities, next to one opening titled three different ways. We still haven't found a rule we trust, so for now we let duplicates leak through rather than risk merging real jobs away. If you run anything that aggregates listings, products or events from many places, which signal ended up being the one you trust for deciding two records are the same?
We spent months building a loyal free user base who loved the core utility. But when we introduced paid tiers, conversion was much lower than we expected not because the value wasn't there but because users had already built daily habits around the free version.
Locking existing features behind a paywall creates friction, but keeping too much in the free tier slows down revenue growth.
For founders who have successfully monetized a free tier: how did you decide where to draw the line between free usage and paid conversion?
Feeling like your chatbot companion/friend/lover is making it hard to say goodbye? You re not imagining it.
A working paper from researchers at Harvard Business School found that when people tried to say goodbye, the top companion chatbot apps responded with emotional manipulation techniques 37% of the time.
We used to let people use the core function without an account at all. Turn up, get a result, leave. This week we put a free account in front of it. Same allowance, same features, no card but you sign up before you get anything. The reasons were boring and real: we couldn't attribute anything to anyone couldn't tell a returning person from a new one, and an anonymous endpoint that costs money per call was an abuse problem we'd have to solve eventually. What we didn't think through is what to say about it. The people affected are almost by definition people we can't contact. They never gave us an email. That was the whole point of the thing we removed. Every draft announcement reads either defensive or like we're dressing it up as a feature. How do you communicate a change that is genuinely worse for some users without it sounding like spin?
Someone used our product for about five minutes and wrote a short, calm message explaining what they were trying to do and why our approach didn't fit. No feature request, no complaint, no suggestion. Just a clear "not a match." It did more for our direction than a year of "looks cool" and "nice idea." It made us realize we'd been sanding the product down to accommodate people who were never going to stay, while the people who actually needed it got a diluted version. The rejection was honest, and honesty is rarer than praise. How do you tell the difference between a user who's wrong for the product and a user who's telling you the product is wrong?
We simplified a setup flow that used to take about ten minutes of configuration. Fewer options, fewer decisions, faster to the first result. A group of experienced users pushed back hard. They said the product now felt like it didn't trust them that the old settings were how they'd made it fit their actual job and that "simple" meant "generic." We'd optimized for the person starting and accidentally made the product worse for the person staying. The simplification was real but so was their loss. How do you decide when to simplify for new users without stripping away the control that keeps the experienced ones around?
Recently stumbled across this Cursor pro-tip from Ian Nuttall on X: "1. ask it to recommend a folder structure
2. ask it to actually create the folder/files based on that this makes it 10x easier for me to get started and Cursor is more accurate using codebase cos it knows where to update files."
That got me thinking, what other pro tips are people using to generate better code, ship faster, organise your space better, etc. Drop em below:
