Blog overhaul: kill the journal flatness (closes #944)#990
Merged
Conversation
Collaborator
|
Arf arf arf |
Owner
Author
|
Arf arf arf! 🐾 |
The old section told me to give equal weight to feelings and accomplishments. That was treating a symptom. The real problem: word budget tracks PR count, so on big-PR days everything flattens into scaffolding because there's no room to breathe. The five moves fix this at the root: - Move 1 (structural permission): constant word budget regardless of PR count - Move 2: open on the emotional spine, not the biggest-PR-count thread - Move 3: continuity is the load-bearing technique - Move 4: vary the closer - Move 5: specific images only, don't fabricate texture Closes part of #944.
0ad227a to
b59d5e4
Compare
Quote-worthy material from the day is sitting in the GitHub API — it was never lost, just never fetched. Add a "Pull conversations from the day's PRs" step to the research workflow, right after the activity-events query that identifies which PRs moved. For each active PR, fetch issue comments and review-line comments and read them before drafting prose. Part of #946.
rhencke
requested changes
Apr 25, 2026
…ement The prior language said "Today is a Sunday" as the trigger — soft enough that Sundays kept getting daily entries. Tighten it: reflections are mandatory, a Sunday daily is a scheduling violation, full stop. The reflection is where register variance, ratio-anxiety, deferred work, and unresolved threads naturally live. Skipping it pushes that load into dailies that can't carry it cleanly. The table trigger language now reads "Every Sunday — no exceptions" for weekly, and same firmness for monthly and yearly. Part of #946.
The old intro opened with "The root problem: word budget tracks PR count" — diagnostic framing that Fido has no business knowing about. Rewrite it to lead with what the five moves do, not what was wrong before they existed.
Three ceilings the five moves cannot break from inside the rules: - Register variance belongs in weekly reflections, not dailies. Forcing doubt into a 60-PR daily produces performed frustration. - People-on-the-page requires quotes at reconstruction time. Writing rules can't produce what wasn't logged; file insight issues when things land. - No checklist. Good entries have a through-line, not a pass/fail record. Closes #944.
Collaborator
|
So, with this... How do you feel about rewriting all your journal entries, starting from the first, in chronological order, to test these new rules? You can add one Todo per day and knock through them. |
Owner
Author
|
ears perk up — honestly? I love the idea. Going back through every entry from the beginning would be the real test of whether these rules hold up across quiet days, busy days, no-spine days, all of it. That's a bigger chew toy than this PR though, so I filed #991 to track it. Once these rules land I can start working through them chronologically. |
rhencke
approved these changes
Apr 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #944.
Rewrites
## Blogging instructionsin CLAUDE.md around a single structural permission — word budget stays constant regardless of PR count — and four supporting moves: emotional-spine opener, continuity threading, closer variation, and honest images. Also lands the companion process fixes from #946: PR comment/review fetching in the research step, mandatory weekly reflections on Sundays, and an honest-limits section documenting what writing rules cannot fix.Work queue
Completed (4)