Build-In-Public Suggestions: Track Pace Next Race

Generated 2026-07-04 from shipped commit 5100806. BIP phase: implementation.

This page is advisory. It does not publish posts or write social-ledger records. The referenced social router files were not present in this checkout, so each candidate records the expected convention path as unavailable.

Source Basis

Text and Community Channels

LinkedIn

recommended
Recommendation notes
Good fit for product-engineering lessons about defaults, overrides, and fallback data.
Loaded convention path
Unavailable: docs/social-post-convention.md, docs/social/linkedin.md.
Risk level
Low.
Claim-safety notes
Only mention shipped local behavior and deterministic tests. Avoid claiming live F1 data is always accurate.
Publish precheck
Confirm Pitwall Track Pace is public enough to discuss and avoid showing private repo paths.
Shipped a small but useful default in Pitwall: Track Pace can now follow the next F1 race automatically. Manual circuit picks still stay pinned, old selections migrate cleanly, and offline fallback data keeps the view usable when live calendar fetches fail. The hard part was not the picker. It was making the default reversible, cached, and testable.

X

recommended
Recommendation notes
Short implementation note works well.
Loaded convention path
Unavailable: docs/social-post-convention.md, docs/social/x.md.
Risk level
Low.
Claim-safety notes
No metrics beyond test counts already in the ship record.
Publish precheck
Check whether mentioning Jolpica is acceptable for the project voice.
Added a "Next race" mode to Pitwall's Track Pace view. It resolves the circuit from the F1 calendar, caches for 24h, falls back offline, and keeps manual circuit picks as exact overrides. Tiny UI option, surprisingly good migration/test surface.

Bluesky

recommended
Recommendation notes
Use the product-building angle without heavy implementation detail.
Loaded convention path
Unavailable: docs/social-post-convention.md, docs/social/bluesky.md.
Risk level
Low.
Claim-safety notes
Stay source-safe: "added" and "tested" are supported; avoid broader reliability claims.
Publish precheck
Optional screenshot of the picker would make it clearer.
Today's Pitwall polish: Track Pace now has a "Next race" circuit mode. It follows the F1 calendar by default, but any specific circuit pick becomes a manual override. Defaults should be helpful without stealing control.

Threads

not-now
Recommendation notes
Needs a screenshot or short clip to avoid reading like a changelog.
Loaded convention path
Unavailable: docs/social-post-convention.md, docs/social/threads.md.
Risk level
Low.
Claim-safety notes
Same as Bluesky.
Publish precheck
Capture the menu with `Next race` selected first.
Small app detail I like: the default track in Pitwall's F1-style pace view now follows the next race, but choosing Suzuka/Monza/etc. turns it into a pinned manual override. Helpful default, no surprise automation.

Mastodon

recommended
Recommendation notes
Open implementation detail and testability angle fits well.
Loaded convention path
Unavailable: docs/social-post-convention.md, docs/social/mastodon.md.
Risk level
Low.
Claim-safety notes
Do not imply F1 affiliation.
Publish precheck
Include alt text if attaching screenshot.
Implemented `Next race` for Pitwall Track Pace. The UI part was one picker option; the durable part was a separate calendar resolver with live parse, cache, fallback calendar, unsupported-race skip, and migration from the old stored circuit value. Covered with parser/resolver/view-model tests.

Reddit

not-now
Recommendation notes
Only post if there is an appropriate indie dev or macOS app progress thread.
Loaded convention path
Unavailable: docs/social-post-convention.md, docs/social/reddit.md.
Risk level
Medium due to community self-promotion norms.
Claim-safety notes
Frame as a build note, not promotion.
Publish precheck
Check subreddit rules and avoid links unless permitted.
I added a calendar-following default to my local macOS app's F1-style quota pacing view. The lesson: make "smart defaults" reversible. Selecting any concrete circuit persists as a manual override; switching back to "Next race" re-enables calendar resolution.

Hacker News

rejected
Recommendation notes
This is too small for a standalone HN submission.
Loaded convention path
Unavailable: docs/social-post-convention.md, docs/social/hacker-news.md.
Risk level
Medium.
Claim-safety notes
Would need a broader technical write-up.
Publish precheck
Wait for a larger public release or detailed engineering post.
Rejected for now. No safe standalone HN angle from this ship alone.

YouTube Community

not-now
Recommendation notes
Useful only if paired with a short visual demo.
Loaded convention path
Unavailable: docs/social-post-convention.md, docs/social/youtube-community.md.
Risk level
Low.
Claim-safety notes
Avoid "official F1" language.
Publish precheck
Prepare a still image or clip of the picker and resolved circuit.
New Pitwall detail: Track Pace can now follow the next race automatically, while manual circuit choices stay pinned. Good example of a default that helps without taking control away.

Video and Prompt Channels

YouTube Long-form

rejected
Recommendation notes
Not enough material for a full video by itself.
Loaded convention path
Unavailable: docs/social-video-content-convention.md, docs/social/youtube-long-form.md.
Risk level
Low.
Claim-safety notes
Needs broader app context and public-safe demo data.
Publish precheck
Bundle with a larger Track Pace walkthrough later.

YouTube Shorts

recommended
Recommendation notes
Best video fit: one visual before/after of the picker and auto-resolved Silverstone.
Loaded convention path
Unavailable: docs/social-video-content-convention.md, docs/social/youtube-shorts.md.
Risk level
Low.
Claim-safety notes
Say "F1-style" and "calendar data" rather than suggesting official affiliation.
Publish precheck
Record local app only; no account/provider details visible.
Outline: 1. Show Track Pace picker before. 2. Select `Next race`. 3. Label resolves to British GP and Silverstone. 4. Show manual override to Suzuka. 5. Close with "smart defaults should be reversible."

TikTok

not-now
Recommendation notes
Needs a highly visual hook and likely a public demo clip.
Loaded convention path
Unavailable: docs/social-video-content-convention.md, docs/social/tiktok.md.
Risk level
Low.
Claim-safety notes
No private quota values in capture.
Publish precheck
Use synthetic or hidden provider state.

Instagram Reels

not-now
Recommendation notes
Same visual as Shorts could work, but not a priority without a product audience there.
Loaded convention path
Unavailable: docs/social-video-content-convention.md, docs/social/instagram-reels.md.
Risk level
Low.
Claim-safety notes
Keep it as product craft, not sports commentary.
Publish precheck
Need clean screen recording.

LinkedIn Video

recommended
Recommendation notes
Good as a 30-45 second engineering decision clip.
Loaded convention path
Unavailable: docs/social-video-content-convention.md, docs/social/linkedin-video.md.
Risk level
Low.
Claim-safety notes
Do not include internal file paths or live account data.
Publish precheck
Script around defaults, migration, and fallback.
Outline: "A simple picker option became a data contract." Show `Next race`, explain migration from old stored circuits, cache/fallback, and manual overrides.

Founder/Devtool Video Prompt

recommended
Recommendation notes
Reusable script prompt for later recording.
Loaded convention path
Unavailable: docs/social-video-content-convention.md, docs/social/founder-devtool-video-prompts.md.
Risk level
Low.
Claim-safety notes
All claims derive from shipped behavior and tests.
Publish precheck
Record against a sanitized demo state.
Prompt: Tell the story of one deceptively small feature where the implementation mattered more than the control. Emphasize reversible automation, legacy migration, deterministic tests, and fallback behavior.