Engineers Are Addicted to Being Useful—Voice AI for Demos Proves Why Guidance Must Read Reality, Not Generate Responses

# Engineers Are Addicted to Being Useful—Voice AI for Demos Proves Why Guidance Must Read Reality, Not Generate Responses *Hacker News #2 (117 points, 70 comments, 3hr): Staff engineer admits "I'm addicted to being useful" and shaped his career around it. Comments reveal most engineers are driven not by money or ambition, but by an internal compulsion to solve problems. This is why demo guidance must read the DOM—users crave usefulness, not conversations.* --- ## The Confession: "Like Akaky Akaievich, I'm Dysfunctional" A staff software engineer wrote an article titled "I'm addicted to being useful" and it hit #2 on Hacker News. The confession: "It's hard for me to see a problem and not solve it. This is especially true if I'm the only person (or one of a very few people) who could solve it, or if somebody is asking for my help. **I feel an almost physical discomfort about it**, and a corresponding relief and satisfaction when I do go and solve the problem." He compares himself to Akaky Akaievich from Gogol's short story *The Overcoat*—a man stuck in a dead-end copyist role who loves his work so much that if he has no work to take home, he does recreational copying just for his own sake. **His framing:** "Like Akaky Akaievich, I don't mind the ways in which my job is dysfunctional, because it matches the ways in which I myself am dysfunctional: specifically, **my addiction to being useful**." ## The Pattern: Not Money, Not Ambition—Just Solving Problems The author reveals what actually motivates most software engineers: "This isn't true of all software engineers. But it's certainly true of many I've met: if not an addiction to being useful, then they're driven by an addiction to solving puzzles, or to the complete control over your work product that you only really get in software or mathematics. **If they weren't working as a software engineer, they would be getting really into Factorio, or crosswords, or tyrannically moderating some internet community.**" The pattern is internal compulsion, not external reward. **The metaphor:** "I'm kind of like a working dog, in a way. Working dogs get rewarded with treats, but they don't do it *for* the treats. **They do it for the work itself, which is inherently satisfying.**" This explains why software engineers often work on side projects, contribute to open source, or help strangers debug code online for free. The work is the reward. ## The Three Addictions That Drive Engineers ### Addiction #1: Being Useful "It's hard for me to see a problem and not solve it." **Manifests as:** - Answering questions on Stack Overflow - Fixing bugs nobody assigned you - Writing documentation for tools you built - Helping teammates debug issues - Building tools that solve recurring problems **The reward:** Someone needed help. You provided it. Problem solved. ### Addiction #2: Solving Puzzles "They're driven by an addiction to solving puzzles." **Manifests as:** - Optimizing algorithms for no business reason - Refactoring code until it's "elegant" - Solving LeetCode problems for fun - Building Conway's Game of Life in obscure languages - Spending 10 hours debugging a 1-line fix **The reward:** The puzzle is solved. The pattern is clear. The code works. ### Addiction #3: Complete Control "The complete control over your work product that you only really get in software or mathematics." **Manifests as:** - Rewriting libraries instead of using existing ones - Building personal tools from scratch - Rejecting frameworks to "do it properly" - Obsessing over perfect git commit messages - Creating elaborate build systems **The reward:** You made it. You control it. It does exactly what you want. ## Why "What Ought to Motivate" Doesn't Match Reality The author makes a critical observation: "There's a lot of discussion on the internet about what **ought** to motivate software engineers: money and power, producing real value, ushering in the AI machine god, and so on. But what **actually does** motivate software engineers is often more of an internal compulsion." **The disconnect:** - What tech companies think motivates engineers: Equity, titles, impact - What actually motivates engineers: Solving interesting problems, being useful, controlling their work This is why perks like "unlimited PTO" and "free snacks" miss the point. Engineers want: - Autonomy to solve problems their way - Interesting technical challenges - Ability to be useful without bureaucracy ## The Three Career Strategies Born from "Addiction to Being Useful" The author reveals how he shaped his career advice around managing his compulsion to be useful: ### Strategy #1: Protecting Time from Predators From his article "Protecting your time from predators in large tech companies": **The problem:** "Some people in tech companies will identify people like me and wring us out in ways that only benefit them." **Predator patterns:** - Manager assigns you every urgent bug because "you're reliable" - Teammate asks "quick questions" that consume hours - PM routes all escalations to you because you always respond - Stakeholders bypass your manager to get direct answers **The trap:** Your usefulness becomes your cage. You solve everyone's problems but make no progress on your own goals. ### Strategy #2: Avoiding the JIRA Ticket Party Trick From his article "Crushing JIRA tickets is a party trick, not a path to impact": **The problem:** "I need to be useful **to my management chain**, not to the ticket queue." **Ticket addiction patterns:** - Closing 50 tickets a sprint feels productive - Inbox zero for bug reports gives satisfaction - Being "the person who gets stuff done" feels validating - Immediate feedback loop (ticket closed = problem solved) **The trap:** You become the most productive IC who never gets promoted. Your manager's goal isn't ticket velocity—it's delivering features that matter to the business. ### Strategy #3: Impressing People You Don't Respect From his article "Trying to impress people you don't respect": **The problem:** "I'm compelled to be useful to some people who I may not respect or even like." **Compulsion patterns:** - Tech lead you disagree with asks for help—you still solve it - PM with bad judgment requests analysis—you still deliver it - Manager who doesn't understand the work asks questions—you still answer thoroughly **The trap:** You're useful to everyone, which means you're strategic to no one. ## Why This Explains the Broken State of Product Demos The "addiction to being useful" pattern reveals why most product demos fail: ### The Engineer's Compulsion = The User's Expectation **Engineers want to be useful:** - Solve problems immediately - Provide accurate answers - Deliver exactly what's needed - No wasted time or effort **Users want the same from demos:** - Understand the product immediately - Get accurate information - Learn exactly what they need - No wasted time or conversations **The parallel:** Engineers are addicted to being useful. Users are addicted to receiving usefulness. ### Chatbot Demos Break the Usefulness Contract **Chatbot demo pattern:** 1. User arrives wanting to understand the product 2. Chatbot asks: "What would you like to know?" 3. User must formulate a question 4. Chatbot generates an answer (may or may not be accurate) 5. User must verify the answer against the page 6. Repeat **Why this breaks usefulness:** - User does the work (thinking of questions) - Chatbot provides uncertain value (generated answers) - User must verify accuracy (checking hallucinations) - No immediate problem solving (conversation overhead) **From the article:** "I feel an almost physical discomfort about it, and a corresponding relief and satisfaction when I do go and solve the problem." Chatbots create discomfort (uncertainty about accuracy) without relief (immediate problem solving). ### Voice AI Delivers Usefulness **Voice AI pattern:** 1. User arrives wanting to understand the product 2. Voice AI reads the page structure 3. User asks: "How does this work?" 4. Voice AI: "The dashboard shows three main sections: [reads actual headings from page]" 5. User understands immediately (no verification needed) **Why this delivers usefulness:** - User gets immediate answers (no conversation overhead) - Voice AI provides accurate information (reading DOM, not generating content) - User can trust the guidance (no hallucination risk) - Problem solved instantly (understands the page structure) ## The Working Dog Principle The author's metaphor reveals the core principle: "I'm kind of like a working dog, in a way. Working dogs get rewarded with treats, but they don't do it *for* the treats. **They do it for the work itself, which is inherently satisfying.**" ### Working Dog Pattern = Good Engineer Pattern **Border collie herding sheep:** - Sees sheep scattered (problem identified) - Moves to correct position (strategy formed) - Herds sheep into pen (problem solved) - Reward: The sheep are where they should be **Engineer fixing bug:** - Sees broken feature (problem identified) - Traces root cause (strategy formed) - Writes fix and deploys (problem solved) - Reward: The feature works correctly **The satisfaction isn't the treat (praise, bonus, promotion). The satisfaction is the work itself.** ### Working Dog Pattern = Good Demo Guidance Pattern **Voice AI guiding user:** - Sees user on pricing page (context identified) - Reads page structure (information gathered) - Describes plans and features (guidance delivered) - Reward: User understands the options **The satisfaction isn't engagement metrics (time on page, messages sent). The satisfaction is usefulness itself.** ## The Three Traps of "Being Useful" The author warns about how the addiction to being useful can be exploited: ### Trap #1: Predators Who Exploit Your Usefulness **From large tech companies:** - Manager loads you with urgent work because you always deliver - Teammates route problems to you because you always solve them - Executives ask you directly because you always respond - On-call rotation becomes "just ask [your name]" **The pattern:** Your usefulness becomes their dependency. You become a single point of failure. Your addiction prevents you from saying no. ### Trap #2: Ticket Queues That Feel Productive But Aren't **The JIRA trap:** - Closing tickets feels satisfying (immediate feedback) - Inbox zero feels productive (visible progress) - Being "the person who gets stuff done" feels validating (social reward) - Velocity metrics reinforce behavior (quantified usefulness) **The problem:** "I need to be useful **to my management chain**, not to the ticket queue." Management doesn't care if you closed 50 tickets. They care if you delivered the feature that unlocked $1M ARR. ### Trap #3: Being Useful to People You Don't Respect **The compulsion:** - Bad manager asks question → You answer thoroughly - Clueless PM requests analysis → You deliver detailed report - Incompetent tech lead needs help → You solve their problem **The cost:** You're spending your usefulness on people who won't help your career, while neglecting people who would. ## Why Chatbot Demos Are the "Ticket Queue Trap" for Users The JIRA ticket trap mirrors the chatbot demo trap exactly: ### JIRA Ticket Trap (For Engineers) **Feels productive:** - 50 tickets closed this sprint - Inbox zero achieved - Teammates thanking you - Velocity chart trending up **Actually counterproductive:** - No progress on strategic projects - Management doesn't notice ticket velocity - No promotable work completed - Burned out from reactivity ### Chatbot Demo Trap (For Users) **Feels engaging:** - Chatbot responds instantly - Conversation feels natural - Getting personalized answers - AI seems helpful **Actually counterproductive:** - No understanding of actual product - Time wasted verifying hallucinations - Still need to explore page manually - No useful information gained **The parallel:** Closing tickets feels useful but doesn't advance your career. Chatting with AI feels engaging but doesn't help you understand the product. ## Why Voice AI Reads Reality Instead of Generating Responses The article reveals why voice AI must read the DOM instead of generating answers: ### Engineers Want to Be Useful = Voice AI Must Be Useful **Engineer's addiction to solving problems:** - See problem → Feel discomfort → Solve problem → Feel relief - **The work itself is the reward** **User's expectation of demo guidance:** - Have question → Feel confused → Get answer → Feel understanding - **The usefulness itself is the reward** **Voice AI approach:** - User asks question → Voice AI reads page → Describes what exists → User understands immediately - **The accuracy itself provides usefulness** ### Chatbots Generate Responses = Uncertain Usefulness **The chatbot problem:** - User asks question - Chatbot generates answer from training data - User must verify against page - Usefulness uncertain until verified **From the article:** "I feel an almost physical discomfort about it, and a corresponding relief and satisfaction when I do go and solve the problem." **Chatbots create discomfort (uncertainty) without relief (verified answers).** ### Voice AI Reads Reality = Guaranteed Usefulness **The voice AI solution:** - User asks question - Voice AI reads page structure - Describes actual content - User understands immediately **No verification needed. No hallucination risk. Usefulness guaranteed.** ## The Three Lessons for Demo Guidance from "Addiction to Being Useful" ### Lesson #1: Usefulness Is Its Own Reward The author: "Working dogs get rewarded with treats, but they don't do it *for* the treats. They do it for the work itself, which is inherently satisfying." **For demo guidance:** - Users don't want to "engage with AI" - Users want to understand the product - Usefulness is the goal, not the conversation **Chatbot approach:** Maximize engagement (conversation length, messages sent) **Voice AI approach:** Maximize usefulness (accurate guidance, immediate understanding) ### Lesson #2: Compulsion Requires Trust The author: "It's hard for me to see a problem and not solve it... I feel an almost physical discomfort about it." **For engineers:** The compulsion to solve problems requires confidence that the solution is correct. **For demo guidance:** The compulsion to understand requires confidence that the guidance is accurate. **Chatbot problem:** Generated answers create doubt. Users must verify. Compulsion to understand blocked by need to verify. **Voice AI solution:** Read-only DOM access guarantees accuracy. Users can trust immediately. Compulsion to understand satisfied instantly. ### Lesson #3: Avoid the Ticket Queue Trap The author: "Crushing JIRA tickets is a party trick, not a path to impact." **For engineers:** Closing 50 tickets feels productive but doesn't advance your career. **For demo guidance:** Chatting with AI feels engaging but doesn't help users understand the product. **The trap:** Optimizing for what feels productive (ticket velocity / conversation length) instead of what creates impact (strategic work / product understanding). **Voice AI avoids this:** Instead of maximizing conversation, voice AI maximizes understanding by reading page structure and providing accurate guidance. ## The Internal Compulsion Principle The article ends with this insight: "There's a lot of discussion on the internet about what **ought** to motivate software engineers: money and power, producing real value, ushering in the AI machine god, and so on. But what **actually does** motivate software engineers is often more of an internal compulsion. **If you're in that category - as I suspect most of us are - then it's worth figuring out how you can harness that compulsion most effectively.**" This applies to demo guidance: **What tech companies think motivates adoption:** - Flashy AI features - Conversational interfaces - Engagement metrics - "Personalization" **What actually motivates adoption:** - Understanding the product quickly - Accurate information immediately - Trustworthy guidance - No wasted time ## Why "Being Useful" Means "Reading Reality" The author's three career lessons reveal why voice AI must read the DOM: ### Career Lesson #1: Protect Your Time from Predators **For engineers:** Don't let your usefulness become exploitation. Say no to requests that don't serve your goals. **For demo guidance:** Don't let conversation overhead waste user time. Provide answers immediately without requiring questions. **Voice AI approach:** Read page structure proactively. No need to ask "What do you want to know?" Just describe what exists. ### Career Lesson #2: Be Useful to Your Management Chain, Not the Ticket Queue **For engineers:** Ticket velocity doesn't matter. Impact on business goals matters. **For demo guidance:** Conversation length doesn't matter. Product understanding matters. **Voice AI approach:** Optimize for understanding (reading DOM accurately) not engagement (extending conversation). ### Career Lesson #3: Don't Waste Usefulness on People Who Won't Appreciate It **For engineers:** Being useful to a bad manager doesn't advance your career. **For demo guidance:** Being conversational with a confused user doesn't help them understand the product. **Voice AI approach:** Be useful in the way that matters - accurate guidance about what's actually on the page. ## The Three Patterns of Internal Compulsion ### Pattern #1: Addiction to Being Useful (Engineer) - See problem → Feel discomfort → Solve problem → Feel relief - **The work is the reward** ### Pattern #2: Addiction to Understanding (User) - Have question → Feel confused → Get answer → Feel clarity - **The understanding is the reward** ### Pattern #3: Addiction to Accuracy (Voice AI) - User asks question → Read DOM → Describe reality → User understands - **The usefulness is the reward** ## The Verdict: Usefulness Requires Reading Reality The HN article proves that engineers are driven by an internal compulsion to be useful. Users have the same compulsion to understand. **The parallel:** - Engineers feel discomfort seeing unsolved problems - Users feel discomfort experiencing confusion - Both crave relief through useful solutions **Chatbot approach:** - Generate answers from training data - Create uncertainty about accuracy - Require verification against page - Delay relief (understanding) **Voice AI approach:** - Read page structure directly - Guarantee accuracy (no generation) - No verification needed - Immediate relief (understanding) The author's career advice applies to demo guidance: **For engineers:** Harness your compulsion to be useful effectively (protect time, focus on impact, work with people you respect) **For demo guidance:** Harness users' compulsion to understand effectively (read DOM directly, provide accurate guidance, don't waste time with conversations) ## The Alternative: Generating Answers Users Can't Trust Imagine if the author's engineering advice was: **Bad career advice:** - Solve every problem anyone asks you to solve (no prioritization) - Maximize ticket velocity regardless of business impact (optimize wrong metric) - Be equally useful to everyone regardless of their respect for you (wasted effort) **Why this fails:** Usefulness without strategy leads to exploitation and burnout. Demo guidance has the same failure mode: **Bad demo guidance:** - Answer every question users ask (reactive, not proactive) - Maximize conversation length regardless of understanding (wrong metric) - Generate responses without regard for accuracy (wasted user time) **Why this fails:** Engagement without usefulness leads to frustration and abandonment. Voice AI provides the strategic version: **Strategic demo guidance:** - Read page structure proactively (no need to ask what user wants) - Maximize understanding, not conversation length (right metric) - Guarantee accuracy by reading DOM (useful immediately) **Why this works:** Usefulness without overhead leads to understanding and trust. ## The Pattern: Addiction to Usefulness Requires Trust Engineers are addicted to being useful because solving problems provides inherent satisfaction. Users are addicted to understanding because clarity provides inherent relief. **Both addictions require trust:** - Engineers must trust their solution is correct - Users must trust the guidance is accurate **Chatbot demos break trust:** - Generated answers may be hallucinated - Users must verify against page - Uncertainty blocks satisfaction **Voice AI preserves trust:** - Reading DOM guarantees accuracy - No verification needed - Immediate satisfaction The author: "I feel an almost physical discomfort about it, and a corresponding relief and satisfaction when I do go and solve the problem." Voice AI delivers relief by reading reality instead of generating uncertainty. --- *Demogod's voice AI reads your site's DOM directly—delivering the usefulness engineers are addicted to providing and users are addicted to receiving. One line of code. Zero generated answers. [Try it on your site](https://demogod.me).*