Add "Work loudly" draft post#1900
Merged
Merged
Conversation
Draft essay on making remote work visible as you do it. Gated with published: false until ready to go live; uses the standard pre-launch BookCta teaser. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add six sentence-case H2s matching the blog's heading style. Rework the bear-bell metaphor so the bell warns the bears (surprise-prone stakeholders who lash out), not fellow hikers. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Readers tune out content below the divider, so surface the book CTA right after the post body where it's more prominent. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- script/analytics.mjs: query Web Analytics (RUM) via the GraphQL API, filtered by host, with top pages/referrers/countries/devices/browsers and a daily trend; resolves the account tag dynamically (no secrets). - npm run analytics alias. - CLAUDE.md: qualitative observations on what the most-read posts tend to share, as a lens for weighing new post ideas. - .gitignore: ignore .env and the local analytics-report.md (keeps specific stats out of the public repo). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Audit pass against the writing style guide: - Add three firsthand beats: the GitHub issues habit, the two-styles team vignette, and the CEO/GC launch ambush that earned the bear-bell metaphor; close the payoff section on the open/inner-source joke - Rework the ending into "The trail test" (manager writes your review from the trail) so it calls back to the opening review scene, and make the sign-off a shareable :quote - Add internal links (showing your work, rules of communicating, why async) and a bolded screenshot-able takeaway - Honor custom Vale rules: drop "rule of thumb" and sentence-initial "So" Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Point 'showing your work' at #the-value-of-showing-your-work and 'without surveilling' at #working-asynchronously. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sets bookRelation: adapted so the auto-appended BookCta says the post is adapted from Open & Async — a soft marketing hook. Renders once the CTA plumbing (#1908) lands on main. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Owner
Author
|
Added |
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
1 participant
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.
New post: Work loudly — why going remote quietly erases your visibility, and how to get it back by narrating the work as you do it instead of writing the big summary after.
The argument: in an office, some of your visibility was free — people saw you at the whiteboard, overheard you unblock someone in the kitchen. Go remote and that ambient signal drops to zero. The work doesn't get less valuable, just less visible — and invisible work may as well not have happened once review season comes around. The fix is to work in the open: the issue you open before you know the answer, the PR that explains the why and not just the diff, the "here's where I'm stuck" in a public channel instead of a DM. Do the work where it leaves a trail.
It's framed around a bear bell — you ring it so nobody gets startled rounding a blind corner, because the danger in an org isn't the stakeholder, it's the surprised stakeholder. Includes a couple of firsthand GitHub stories, including one that didn't go well.
Adapted from a chapter of the book (bookRelation: adapted), so it picks up the "adapted from a chapter" BookCta automatically. Publishes live on merge at /2026/07/14/work-loudly/ — the canonical the dev.to cross-post points at.