Byline: Paul Keen, and the voice that a byline requires

[pftg]

Byline: Paul Keen, and the voice that a byline requires

Paul: "you can use my name." All three posts now carry author: "Paul Keen",
matching the paul_keen record already in data/authors.yaml and the seven
existing posts that use it. Verified rendering - the page shows "by Paul".

A name on the byline is not just a frontmatter change, so three things moved
with it.

First person where the sentence is a judgement. "We think it is the
highest-return two minutes" became "I think". "It is the only thing that
distinguishes a ratchet from a decoration" became "as far as I can tell it is
the only thing separating". Kept "we" wherever it describes what the firm
actually does - we stopped a change in review, we ran the exercise. The
distinction is: "we" for actions the team took, "I" for opinions someone is
staking their name on.

Cards on the table, the Arkency move. The AI-review post now opens by
disclosing the conflict before making the argument:

Cards on the table before I start: I run a development shop, and this post
argues you need experienced people reviewing AI output. That is convenient
for me. So I am going to make the case with a diff you can check yourself,
and if the Rails reasoning does not hold up, none of the rest should
persuade you either.

That was Sample 4's strongest lesson and it was unusable while the byline said
"JetThoughts Team" - a company noun cannot disclose an interest or stake a
reputation. Now it can.

An admission that costs something, in the same post's close: expertise
"is an awkward thing to sell and an awkward thing to measure. I would still
rather tell you that than quote you a velocity number."

Gates: cadence quotas pass in every section of all three - two failed after the
first-person edits (a section lost its short sentence) and were fixed, not
waived. Slop measurement clean on all three: zero negative parallelism, zero
definitional cadence, zero generalized actors, openers within caps.
bin/hugo-build green. marketing_copy_test 5/13/0. bin/rake test:links clean at
31,948 unique links, zero errors.

FLAGGED, not fixed - out of scope for a byline change, and Paul's data to
decide on. data/authors.yaml line 5 says Paul has "22+ years" experience,
which matches claims-canon; line 7 says experience_years: 15, which
contradicts it. The field is referenced by no template in themes/ or layouts/,
so nothing publishes the wrong number today. It is a dormant defect: the moment
someone renders that field we publish 15 against a canon of 22+. Canon also
says derive tenure rather than hardcode it, so the fix is probably deletion
rather than correction.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session: https://claude.ai/code/session_016PUkwFTsiv7EB2DYKogbpg

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 1cde0e9e-8f6c-44c8-ad5a-fbd67ecee4ab

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}