May 18, 2026
Asked a question? Prepare for vibes
Don't Answer the First Question
Tech advice or quiet condescension? Commenters clash over asking “why” before helping
TLDR: The essay argues that when people ask for the wrong thing, the smartest response is to ask what problem they’re really facing first. Commenters split hard: some called it thoughtful and humane, while others said it risks sounding smug to anyone who already knows what they’re doing.
A software engineer’s essay about a deceptively simple rule — don’t answer the first question right away — has turned into a full-on comment-section philosophy fight. The author says that when someone asks for something odd, like splitting a huge performance log into smaller files, the better move is to ask why they need that in the first place. In plain English: don’t just hand over the button they asked for; find out what problem they’re actually trying to solve. The goal, they argue, is better tools, better understanding, and fewer wild-goose chases.
But the crowd was very split on whether this is wise mentorship or just an elegant form of talking down to people. One camp applauded the approach, with one commenter saying this is exactly how helpful answers should work — especially after years of internet forums like Stack Overflow becoming infamous for the maddening vibe of, “You shouldn’t do that, so I won’t tell you how.” Another side was instantly suspicious, warning that if you pull this move on people who already know what they’re doing, it can come off as undermining, patronizing, and deeply irritating.
There were lighter moments too: one commenter compared the whole thing to the teaching style of beloved explainer Julia Evans, which is basically the internet’s highest compliment for clear thinking. And then, in classic comment-thread chaos, someone swerved into a side rant about companies desperately slapping “AI agents” onto boring products to sound relevant. In other words: one thoughtful essay, and the community somehow delivered therapy, trauma, praise, and AI-branding cynicism all at once.
Key Points
- •The article uses a common Perfetto support question about splitting trace files to illustrate a broader method for handling unusual user requests.
- •The author says unusual questions should prompt follow-up questions about the underlying problem rather than an immediate direct answer.
- •The article argues that these conversations help both users and product builders by improving user understanding and exposing areas where the product is confusing or incomplete.
- •A mental checklist is described for evaluating unusual questions, including whether the request is common, reasonable, and aligned with the tool’s architecture.
- •The article gives Perfetto trace analysis as an example where users may try to derive every metric from traces, even though trace collection and processing are costly compared with dedicated metric systems.