... fully engineer away. Mine is low but it isn't zero, and when it misses, the user has already spent one of a small number of credits. I've gone back and forth on this and landed somewhere I'm still not sure about. What I considered: Free retries. Cleanest for the user and the one I wanted. The problem is a retry costs me exactly what the original cost, and "free" has no natural stopping point someone who doesn ... ... automation. Doesn't scale, but might be correct at my size. Where I'm stuck is that I can't measure the thing I'd need to decide. I don't know what share of retries are genuine misses versus

... leadership." Copy, paste, post. Zero lived experience, zero original thought. It's just AI slop in a blazer. AI-written emails to people who matter. Your client can tell. Not because the grammar's off because the warmth is. VS GOOD AI JUDGEMENT Using AI to actually look at what a candidate did. Not keyword-matching a CV pulling apart their portfolio, cross-referencing their claims. You still decide. You just decide better. Using AI to draft, then making ... ... wrong is huge. the tool might be capable but the stakes still matter. Comment from Omri Ben-Shoham(@omri_ben_shoham1): One I'd add, from actually running scheduled agents unattended: bad AI judgement is letting it run autonomously somewhere

... been building ProductBridge as an AI-native alternative to traditional customer-feedback tools. But we don t want polite founder feedback. We want to understand what would genuinely make a team abandon its existing feedback platform and move somewhere

... more conversations I look at across places like Reddit, LinkedIn, X, Product hunt, Bluesky and different communities, the more I m starting to question that approach. People constantly talk about problems they re having. They ask for alternatives to products they already use. They look for recommendations. They complain about workflows. They ask if there s a tool that can solve a specific problem. Most of these conversations probably never make it into a traditional lead database. And that ... ... find conversations where attention and demand already exist? I'm curious how other founders think about this. Where have you found your best customers so far? Cold outreach, communities, Reddit, LinkedIn, X, Product Hunt, referrals, content - or somewhere

... from Analytics, re-enter them into a Sheet for the report, check the CRM to see which leads came from which campaign, copy that into the same Sheet, then open the content tool to see what actually went out versus what I thought went out. By the time I finished the report it was almost noon. I hadn't done anything yet. The AI tools made it worse before they made it better. They were good at writing a draft ... ... Then I'd take the draft, paste it somewhere

... keep digging into what actually gets a product mentioned in ChatGPT or Perplexity answers, and the data keeps pointing somewhere that makes me question the whole "GEO/AEO" hype. Ahrefs looked at 75k brands and found branded mentions correlated with AI visibility way more than backlinks 0.664 vs

... Thanks a lot for supporting and for being in the SKI community. This is a guide to get started, just in case you are stuck somewhere. This guide covers how to get started with voice coding. This guide can be used to connect projects which you already are working on, to SKI. Download SKI (if you haven't already) Currently available on Mac (M series) and Windows. Will be launching soon on Linux. Start SKI You will be shown ... ... agent (by voice on SKI) on what updates it should speak out and the agent will adapt accordingly. A simple video tutorial is available at : Let us know if you face any issues or are stuck somewhere

... been using Frame io for client reviews, and while it's good at what it does, I always felt it was missing the bigger picture. Feedback lives in one place, tasks in another, files somewhere else, and client communication somewhere

... means it isn't doing distribution work at all, it's a landing pad for traffic you have to send yourself. Or people don't follow an upcoming page without a reason, and the reason has to come from somewhere else entirely. What I want from anyone who has shipped more than once: did your upcoming page ever produce followers on its own, or did every single one come from a thread, a newsletter, or a specific person ... ... discovery surface of its own nobody browses upcoming, so it's a landing page for traffic you were already going to send. Which means it doesn't replace the scramble on launch morning, it just gives the scramble somewhere

... policy side. You made both points and I do not think you joined them. On defaults following risk class rather than the check result, agreed, and one thing to add. It means the class has to be declared somewhere rather than worked out per action, which is where two other people in this thread also ended up. And it means an action nobody has classified should land on the strict side, for the same reason you gave about failing loudly ... ... nothing, the reviewer's normal experience becomes an empty screen, and empty screens train people to expect empty. Whether the one that is not empty gets read properly on day forty is an open question. It still beats the alternative

... gets even less attention: the moment you store something in the cloud, you're trusting a third party you usually know almost nothing about. Who actually has access to your data on their servers? What happens if a government somewhere issues a request the provider is legally required to comply with, possibly under a gag order you'd never even hear about? How seriously does that provider actually take your privacy versus

... share that I'm hiring!" for the fourteenth time this week. A motivational quote about hustle printed over a sunset. Three humblebrags disguised as life lessons. One "I'm grateful and blessed" announcement with 4,000 likes. And somewhere, buried under all of it, maybe one actually useful post. This is the daily reality of LinkedIn for most programmers. They tolerate it because they feel they have to. They hate it because, honestly, it deserves to be hated. Here ... ... what the actual job entails. Developers have noticed. Only 12% of developers use LinkedIn as their main source of technical information, according to a Stack Overflow survey. Most are on the platform purely because they feel they have no alternative

... just wanted a couple more indicators and to export my data without paying monthly. Second, honestly, I'm not that great at reading charts. It takes years to get good, and I kept second-guessing my entries. So somewhere along the way I started building my own thing instead of complaining about it. The idea was simple: make the charting part free, and put an AI on top that looks at the chart and tells you what it sees - patterns ...

... give some context on how I got here: two years ago we started building fan apps for esports teams like Team Liquid and G2. The whole model relied on getting fans to leave Instagram or X and sign up somewhere new. It worked, but only for the most hardcore fans. Everyone else stayed on socials, where we couldn't reach them. That's been my biggest source of headaches for a while. We were doing the hard part, helping teams ... ... grow huge audiences, then watching most of that traffic drop off because we kept asking people to go somewhere

... anyone in the world click through it. The problem most builders have is not a lack of proof of work. It is that the proof is scattered. A project here. A GitHub profile there. A blog post somewhere else. A startup update buried in an old LinkedIn post. None of it connected. None of it presented as a coherent professional identity. A recruiter or collaborator has to do the work of stitching these fragments together, and most of them will ... ... would hold their attention for twenty minutes instead of forty seconds. That is the entire premise. Not where you've worked. What you've built. The Real Answer Is Not Either/Or In 2026, the strongest combination is not resume versus

... save a lot of photos, files, links, and notes, but later struggle to remember what something was called or where they saved it. That usually means a few extra steps just to find something you already know you kept somewhere. The idea behind Elunimy is to keep everything in one workspace and make it searchable by the smallest detail inside the content itself, not just by title or memory. Even if you don t remember the exact name, you should ... ... again in a simple way. If this sounds familiar, I d be happy to share more and let anyone interested join the waitlist. Comment from Mustafa Arian(@thenameisarian): this resonates. the hardest part of the i saved it somewhere

... user___1702026e6f946759d1d798a): This is also one of the first things investors look for. A polished demo can attract attention, but if someone cannot quickly understand who has the problem, how painful it is, and why the current alternatives are inadequate, the conversation hits a dead end. Based on my own experience and a friend who works at 1752vc, the strongest pitches often make the problem feel inevitable before they spend much time explaining the product. Comment from Briana Pole ... ... that's a very important distinction. That could also explain why you're attracting more men, who are looking for a real solution vs

... feed. Product updates and launch posts have their place, but they reach people only after a builder has established real presence through genuine contribution. You build an audience by being worth following. Then your product posts land somewhere real. The principle: earn reach by contributing value, not by promoting yourself. Why This Is the Right Call Professional networks are built on trust and signal. LinkedIn's core problem is that it became a promotional platform. Everyone is announcing, celebrating, sharing ... ... industry is getting wrong. Build the kind of presence that makes people want to follow you because you are genuinely worth following. Then, when you launch something or hit a milestone, post about it. At that point it lands somewhere

... made them succeed or fail? For those who've sold into small/mid-sized businesses, what's usually the biggest blocker to adoption price, integration effort, or something else? Is there a feature here that seems like a "nice to have" versus something that would actually change behavior? Would appreciate any perspective, whether from experience building similar things or just as someone who's dealt with this as a customer or business owner. Comment from Tommy Kang(@sjtkang): What I'm building ... ... Doing competitor

... rotation. Curious which of yours are keepers versus glue. Comment from Nika(@busmark_w_nika): @zenexpenses  I know only 2 of them, need to do the research of the rest :D Comment from Nika(@busmark_w_nika): @fabian_maume  I would swap spotify for YT music, but we are pretty accurate with a good music :) Comment from Nika(@busmark_w_nika): @ethan_cheng  are there any other alternatives

... must exceed the effective value of the Slot directly above it by at least the platform's Minimum Jump Rate. For example, if Position #5 has an effective value of 100 and the Minimum Jump Rate is 5%, a competitor must reach at least 105 to claim that position. This creates a transparent and predictable ranking system where every movement follows the same public rules. Other users can support Slots they like through Boosts. Boosts work differently from Refuels ... ... when every rule is public? What happens when visibility behaves more like a live market? What happens when communities can directly support what they want to see? I genuinely don't know whether this idea is brilliant, terrible, or somewhere

... externalized summary trail is basically what Pushary is, the per-step handoff lives outside the agent, so awareness persists without bloating the thing that has to stay lean. You're right that you need context maintained locally somewhere, the key word is somewhere

... 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 so they compress the discomfort and move on. Research note: A 2023 Pew Research study found 79% of Americans feel they have little control over data companies collect yet the majority continue using the same platforms. Researchers have called this ... ... privacy fatigue : not indifference, but the behavioral result of repeatedly finding no viable alternative

... prefer to review the output of agents, rather than individual actions, and run one or more sessions in parallel. What type of developer are you when working with AI coding agents? For context, when @Kilo Code launched their new @VS Code extension last week , with parallel agents, inline diff reviewer, and multi-model comparisons, some users actually wanted more control back. While the team is working on multiple improvements , like better diffs before you approve and permission flow fixes ... ... curious about your point of view. How do you like to work with AI coding agents? Comment from Mustafa Najoom(@mustafa_najoom): Somewhere

... Google can still see it WeTransfer is convenient, but they keep logs Slack ? Don't get me started So What's Actually Wrong? The files aren't the problem. Trusting the wrong people with them is. When you upload somewhere, you're asking three things: Does the company actually delete it? Can they read it if they wanted to? What happens if they get hacked? Most services say " yes ," " no ," and " uh ... we'll notify you " (which is terrible ... ... files auto-delete before someone can even download The Real Question Is ANY online file sharing 100% safe? No. Not ours, not anyone's. But the question isn't "is it perfect?" It's "is it better than the alternative