Was sent a link and told to look at it before Tuesday. Their job this afternoon is to answer one question for someone else.
Seeding strength: STRONG on fears and vocabulary, WEAK on the deadline framing.
A founder or a lead sent them a link and said "look at this before Tuesday". They did not choose it and they are not excited about it. They have a working stack and a sprint already full.
Their job this afternoon is to answer one question for someone else: will this cost us a week or an hour.
They know their own stack cold, and they know auth well enough to be suspicious. They have integrated at least one provider before. They read docs by scanning for the code block.
They do not know or care about our pricing, our legal entity, or our brand argument. Those are someone else's column in the spreadsheet.
Not security. Breakage and lies. Their fears are specific, and better-auth's own issue tracker is this person writing them down. Three patterns dominate 300 issues:
The docs do not match the software:
"the documented 200 schema (
redirect_uri, required) does not match the implemented response ({ redirect: boolean, url: string })." — better-auth #10880
A version bump breaks the build:
"Drizzle 1.0 removed
relationsand replaced it withdefineRelations, so the generated file does not compile: '"drizzle-orm"' has no exported member named 'relations'." — better-auth #10924
"We hit this while upgrading a monorepo from 1.6.28." — better-auth #10897
Tooling that fails destructively:
"The output file is opened/truncated before generation succeeds, so the failed run leaves the previously valid schema file empty (0 bytes)." — better-auth #10906
Underneath all three is one fear: that they will be the person who introduced the dependency that breaks the next release.
Measured across 300 better-auth issues: auth appears in 87.3%, session in 35.7%, sign in in 23.0%, login in 14.7%. This is the one population that genuinely says "sign in" more than "login", and I checked it is not merely an echo of the library's signIn() function: 48 of the 61 issues using the phrase contain no such identifier.
They also speak in nouns we can serve: base URL, callback, schema, migration, ORM, monorepo, the generated file, expected behavior, reproduction.
"How long until I have a user signed in, and what will it break?"
Strong on fear and vocabulary: 300 real issues from the better-auth tracker, which is this persona writing in their own words, with measured word frequencies rather than guessed ones.
Known weakness: the "evaluate it by Tuesday" framing is mine, not theirs. I did not find the deadline-pressure voice verbatim in either corpus. The situation is plausible and matches how this reader arrives, but treat it as a stage direction rather than evidence.
Second weakness: this corpus is people who already adopted better-auth and hit a wall. It is excellent for "what breaks" and silent on "what made me choose it". Do not use this persona to judge whether a pitch is attractive, only whether it is credible.
Surface under test: "Land the enterprise deal. / Keep the same bill." with the login-system lede and "Get an instance". This reader ran on Grok.
They comprehended the product but could not tell hosted from library. The headline, in their words, "is not my column." Only Quickstart mattered. They refused "Get an instance" as "create an account with a different label." They wanted a stack name, a code block, and a time-to-first-user.
| Q1 what is it | Q2 do you care | Q3 what next | Left cold by headline |
|---|---|---|---|
| PASS | PASS | PASS | No |
What is this? "It's an auth provider. 'Login for your app' tells me the category flat out, no guessing needed."
Do you care? "Maybe. 'Your database, not ours' is the line that got my attention, not because I care about their pitch on data ownership, but because it tells me something concrete. But I don't see a code block. I don't see a framework name."
What next? "Click 'Set up login' - there's nothing else on this screen that gets me closer to an answer. I want to see if the next screen is a
npm installline or an account-creation form. If it's the latter I'm gone."
What stops you? "No code visible on this first screen. If it asks me to sign up before showing me a quickstart, I'm closing the tab and telling my lead 'didn't get far enough to say.'"
Run 03 tested the three quiet lines on the founders, enterprise and agents doors. This reader does not appear in its score table. Their run-02 objection, that there is no code and no framework name on the first screen, is still open.
Source: readers/04-integrating-developer.md