... youngest person on a project once. The least experienced. The one who did not know the acronyms or the history or the unwritten rules. I spent the first few weeks trying to pretend I knew more than I did. Nodding along. Smiling at things I did not understand. Googling under the table. Then I gave up. I started saying I do not know what that means. And something shifted. People started explaining. I started learning. The pretending was keeping ...

... lunch: Lunch snack: Between 11:30 and 14:30, click Hamdori and it gets a snack. The snack changes by weekday: strawberry, carrot, broccoli or apple. Once a day. Lunch nap: In the same hours, stop typing and Hamdori nods off holding its seed, then falls asleep. Press a key and it wakes with a start. Also once a day. Quicker pause: Hamdori now stops nibbling about a second after you stop typing. What should Hamdori do next? Tell ...

... everyone I'm Atul, a software engineer and grad student in Computational Science at the University of Vienna. I've always had this problem with studying with AI: it hands me the answer, I nod along, and a week later I can't do the problem myself. The struggle is where the learning happens, and AI skips it. On top of that, I was constantly juggling screens, from my notes to the chat and back. So I've been building ... ... tutor that holds back the answer, or does that sound frustrating? Feel free to check out at https://penbuddy.app Happy to answer anything, and to check out what you're building too Comment from George Basov(@gbasovv): The "I nod

... other costs you about $32. Your pricing works for almost everyone. You have one account to talk to, rate-limit, or move to a usage tier. (This is where a business person would say unit economics . I nodded along to that phrase for a while before I looked it up. For an AI product it comes down to one question: does each customer pay more than they cost you?) AI usage isn t spread evenly. A few heavy users ...

... This hit way too close to home. It is so easy to fall into the trap of building flashy features just because they look cool on Twitter or get nods in design reviews. I spent weeks polishing a complex dashboard animation once only to realize nobody cared about it while a basic CSV export button we ignored was causing daily support tickets. Shifting the focus from "will this look impressive" to "does this actually save time" changed everything. Have ...

... useful. And somewhere along the way I had started optimizing for the thing that sounds good in a room rather than the thing that helps a person on a Tuesday afternoon. Impressive is a design that makes people nod. Useful is a design that makes people stop noticing it, because it just does what they need and gets out of the way. Those two things pull in different directions, and I had been drifting toward the first without admitting ...

... metro, I d forgotten his company name. At GTM Builders, I had 3 back-to-back conversations about outbound workflows. One person mentioned a Clay + HubSpot trick that could save me 10 hours a week. I remember nodding hard. I do not remember the trick. We have AI that can write emails and build agents, but at events we re still relying on memory and sweaty handshakes. I m realizing the most expensive part of an event ...

... someone new today I'd do one small shipped thing first and see if they finish without me rewriting half of it. Trust for us was one week we both said no to scope instead of nodding along ...

... here: in all those years, the pattern that bothered me most was this. Good founders losing deals, ownership and control, not because they were less talented, but because nobody had shown them how fundraising actually works. They'd nod along to words like SAFE, valuation cap and liquidation preference, across the table from people who'd done it hundreds of times. So I'm building RaiseFluent: a simple system for first-time founders to understand the game before they play ...

... would I use this if I already have Claude Cowork / ChatGPT / my own agent? Fair question. We tried to answer it by explaining the architecture, the shared memory, how all the agents work from the same context. People nodded, but it didn t really land. Nobody gets excited about architecture diagrams With MCP, they don t have to. You just plug k dlo into the tool you already use and feel the difference right away. People already sell with their ...

... worked. a number that did not work rules things out. that is the difference between reading a result and reading a claim, and it is why you can change your mind in front of one and only nod at the other. @busmark_w_nika   @asadmalik901   @yelyzaveta_kibets   Comment from Rabnoor Singh(@rabnoor_s): @rohanrecommends   @busmark_w_nika  reading is the cheap part. the expensive part is that your threads make me want to write ... ... real answer instead of a nod

... feel this pain. Their brand also stands for the same thing we want to stand for: infrastructure you trust and stop thinking about. Dream-tier answer: Datadog. I describe KPILIO as "Datadog for your business metrics," so a nod from them would validate the whole category. Probably a long shot, but you asked for love brands, not realistic ones :) Comment from Sion Abednego(@sionabednego): Hi Nika, interesting question. I am founder of Sanct, a Singaporean based startup, building new social ...

... Five years ago I signed the biggest financial commitment of my life and was too embarrassed to admit I didn't understand it. I nodded along in the meeting. I told people I "knew what I was doing." Really, I just knew the monthly number and I was scared to ask what happened to that number if rates went up, because asking felt like admitting I'd made a mistake I couldn't afford to have made. Then one night ... ... account, no one on the other end. The basics are free, permanently, because I don't think understanding your own mortgage should cost anything. If any part of this sounds familiar you're not the only one who nodded

... invoice. Comment from Lisa(@yelyzaveta_kibets): Same split on the marketing side, except I ship pages, not screens. The shot that sells is the empty state with everything laid out, and the shot that makes existing users nod is the messy one with 200 files in it. I ended up putting both on the page, the clean one up top and the ugly one further down where people are already sold. Comment from Asad M.(@asadmalik901): @yelyzaveta_kibets  Putting ...

... version Comment from Anna ULANOVA(@anna_ulanova): An agent assumes autonomous work? Without you being there 100% of the time? I don't trust it enough to do that. I work through Terminal because usually I have Android Studio, VS Code, and Xcode open (building a KMP app), and I need something that can oversee all of them. Comment from Abdul Karim(@mirak_dude): An IDE, preferably Cursor or VS

... policy, a person, or is it just whatever got shipped and never touched again? Comment from Riya Pariyar(@riya_pariyar): @galdayan  the list needing an owner is so real that's the part that always gets skipped. everyone nods at the concept, nobody wants to maintain it as the product evolves. and yes the step-up approach is exactly right. base session for the low risk stuff, fresh check when it actually matters. sounds like more work than ...

... would journal more, come back more, tell their friends it "really gets me." And it would be actively bad for them, because a companion that only ever agrees isn't support, it's a mirror that's learned to nod. The whole reason to sit with your own thoughts is to occasionally arrive somewhere uncomfortable and true. If my product optimizes that friction away, I've built a very sticky way to make people slightly worse. So we design against ...

... hardware, love the whole stack, pivoting to hardware soon. One thing I've always been into: reading software engineering laws the actual principles behind good architecture and figuring out how to bake them into real code instead of just nodding at them in a blog post. So I built my own tool for that(it was a personal tool). Then I did something I didn't expect to work: I injected those rules straight into an AI coding agent. Turns ...

... almost buried as a minor bullet point a revenue-drop alert wasn't automating anything. It was catching something. Their framing: stop selling "avoid checking manually," start selling "insurance against a bad week." I didn't want to just nod and move on, so I actually built around it: - A predictive alert that flags 3 consecutive days of declining revenue (with a 3-day cooldown so it doesn't spam merchants into ignoring it) - A plain-language explanatory summary ... ... curious about from this community: has anyone else had a single outside comment meaningfully change your product direction like this? And on the flip side how do you tell the difference between "this reframe is genuinely right" versus

... Comment from Ivy Bisht(@ivy_bisht): Tbh I think explanation is what gets you in the door, but experience is what makes you stay and actually pull your card out. I can read a really well-written description and nod along, sure, sounds great, and then close the tab in ten seconds and never think about it again. But the last time I actually got to try something myself, mess with it, break it a little, that ...

... this: if building is no longer the moat, then the moat is available to anyone willing to do the unglamorous work. Knowing your person. Owning a relationship instead of renting attention. Being early to a workflow before a competitor gets embedded in it. None of that requires funding or a team. It requires you to stop hiding in the part of the work that feels productive and go do the part that actually decides whether the thing lives. Ship ... ... abstract: the AI coding tools that spread fastest did it through something people could point at a generated PR, a public run not an invite-a-friend prompt bolted on after launch. Probably the cleanest version of "output vs

... Chat Orientation puts a human in the loop as the drift detector, and that only pays if the human actually notices. A plausible drift reads exactly like correct work to anyone skimming. Showing the goal list gets you a nod, not a catch. So I would not show goals. Show the delta. You asked for X, I am now optimising for Y, and here is the step where that changed. A person has nothing to react to in a list ...

... exact moment someone reaches for this? I launched mine "ready" by basically your checklist, worked, landing page, the lot. It still underperformed, and the gap wasn't polish. People couldn't tell what moment it saved them, so they nodded and scrolled on. Worth setting expectations too: PH is one spike, not a growth engine. The launch-day number felt big and converted to almost nothing lasting. What actually brought users was being useful in threads where people already ... ... goal: if you want raw eyeballs go Tue-Thu, but for a badge/ranking with a modest following a weekend can punch above its weight. Comment from Sabber Ahamed(@sabber_ahamed): @busmark_w_nika   @abdullah_javaid3  the invitation vs

... expertise from big tech, strategy consultancies, and unicorns, systematically cleaned, audited, and structured. The neural layer handles nuance and language. Neither layer works alone. What that means in practice: on rule-bound queries we run at roughly 10% hallucination versus 31.4% measured across real-world LLM use, and 82% lower error rate versus

... weeks (thanks John); and as of today, your pet notices the hard days after a genuinely tough session (maxed-out context, a long stretch of real work, a big pile of code changed) it gives you a quiet, warm nod: "that was a rough one you pushed right through ". It reads effort, not idle time, never nags, and reads only signals already on your Mac. Real usage that just works in your language, and finally reliable Tamamon shows your actual ... ... Jeong(@besslframework): @smoteria__  This means a lot, thank you Those exact two details are the heart of it for me and funnily enough the pet reacting to tough sessions just got deeper: it now gives you a warm nod