Source for bip-draft.yml — the workflow picks Day N = (day-of-year mod 30).
One section per day; each draft gets auto-enriched with yesterday’s commits.
Voice rule: drafts are scaffolding — rewrite at least one sentence in your own words before posting.
Screenshot/diagram of the project constellation (linux-aegis, talus, externum, fortis, quantum-shield, NV2). One line each: what problem it kills. End: “which one should I deep-dive first?”
Post one real metric (192 externum tests, boot log timing, benchmark ops/sec). Explain why that number was hard to get. Never fake precision — say “measured on my machine, config in repo”.
How linux-aegis ships as four patches against upstream instead of a DKMS out-of-tree blob. Why “compiles in-tree, boots in QEMU from CI” was the whole battle.
“One of my projects compiles to Python, Bash AND a native binary from the same source. Guess why the Bash backend is the weird one.” Answer in the next post.
Paste a 5-line terminal capture (talus catching a simulated churn burst, NV2 frame times). Caption: what the viewer is looking at in one sentence.
Build in public ≠ posting daily dopamine. I automate drafts and syndication precisely so the writing time goes into the work. Short, honest, no threads-of-threads.
What got shipped this week across all repos (the workflow’s commit list makes this trivial). One paragraph max, links to entity home.
eBPF in 3 sentences for non-kernel people: syscall syscall syscall — police inside the kernel watching every door. Then one line on why that’s fast.
Name one OSS tool that saved you hours this week (crier, git-cliff, libbpf). Genuine recommendation, no affiliation — good-faith networking.
Why quantum-shield derives per-chunk keys instead of one global nonce. The bug class it prevents, in plain language.
Something that broke this week and the fix. The more mundane the better — reliability porn is boring, debugging stories are not.
Line from The Stitcher Trilogy + one sentence on stitching horror with systems-brain discipline. Books and code are the same skill: constraints.
Best visual of the week (NV2 voxel render, root page CRT aesthetic, terminal UI). Let the image do the work.
Ask a real question you have (CO-RE portability across 6.x? ML-KEM key rotation UX?). Answer every reply — questions are the cheapest engagement there is.
Tag/release shipped? Post the changelog’s best three lines. git-cliff makes this a copy-paste.
“You need a CS degree / a budget / a team to build systems software.” You need a kernel tree, QEMU and stubbornness. Show the CI boot log as proof.
One Mermaid diagram (fortis boot chain or NV2 pipeline). Caption: “every arrow is a link in a trust chain”.
The pipeline itself: article → git push → 9 platforms. “I don’t have a marketing team; I have GitHub Actions.” Link the repo.
“Most ‘post-quantum ready’ tools are marketing until ML-KEM is in the default path.” One argument, one caveat, invite pushback.
Three things you actually read this week (patch series, paper, blog). One sentence each on what changed in your head.
Commits + what’s next week. Consistency beats intensity — this is the post that compounds.
KDP dashboard moment, a review, or the process of writing book 2’s ending. Writers on dev Twitter are rare; use that lane.
One actionable tip (e.g., “add llms.txt to your site in 10 minutes”). Pure value post; nothing asked back.
NV2_ENGINE frame time over the month, or externum test count trend. Small chart, big credibility.
Why the projects are named what they’re named (aegis, talus, fortis). Names are free branding; tell the story.
One habit that actually helps devs (verify signatures, zeroize keys, pin CI base commits). No fear-mongering, one concrete command.
“linux-aegis needs SELinux-stacking test scenarios — if you’ve done LSM stacking, I’d love your take.” Specific asks get specific help.
“The Stitcher is a crime-horror trilogy written like a distributed system: state, failure modes, irreversible operations.” Post the good line.
Public TODO for the quarter. Accountability post; people return to check if you did it.
Shout out people who replied/reshared this month. End with the entity home link. The 30-day loop restarts tomorrow.