DEV technical article: human-owned evidence brief
This is a PRIVATE/LOCAL WRITER WORKSHEET TEMPLATE, NOT A DEV post, and not a permission to publish. Keep any unpublished experiment/client details out of public Git. The author writes their own article and verifies every technical statement. If any AI assistance is used, follow the current DEV AI guidance including disclosure and limits on AI promotional articles.
Identity and editorial purpose
Section titled “Identity and editorial purpose”- Approved author/profile:
- Project and confidentiality/publicity status:
- Reader and practical engineering problem:
- Reader’s expected takeaway (independent of the project):
- Type: tutorial / postmortem / verified failure / experiment / discussion
- Original or crosspost? If crosspost, existing canonical source URL:
- Candidate series and up to four true tags:
Evidence inventory (complete before drafting)
Section titled “Evidence inventory (complete before drafting)”| Factual claim | Direct source / exact commit or paper | Environment / measurement period | Verified by owner? | Limitation |
|---|---|---|---|---|
Human author’s structure
Section titled “Human author’s structure”- Precise problem and stakes:
- Reproduction: versions, prerequisites, input, commands:
- Observed result (not a guessed benchmark):
- Why it happened / mechanism with links:
- What did not work and other explanations:
- Trade-offs, safety and limits:
- Useful reader action / genuine technical question:
- Optional relevant affiliation / source link (no backlink farming):
Prepublication gates
Section titled “Prepublication gates”- Source data/public code rights and privacy checked
- Article teaches without requiring reader to adopt author’s product
- Claims, dates and metrics checked by human owner
- Up to four appropriate DEV tags; cover image/source attribution checked
- Existing original URL linked as
canonical_urlonly for actual crosspost - Any AI assistance factually checked and disclosed; article not AI-generated clout or business promotion
- No pasted AI-generated comments; all community replies human-composed
- Author inspected full draft on DEV and chooses native publish/schedule manually
- Native scheduled status/published permalink confirmed before reporting success
Publication and measurement ledger (private)
Section titled “Publication and measurement ledger (private)”- Candidate Italy-local and audience-local time + zone:
- Actual native schedule confirmation (owner observation):
- Actual publication URL (once observed):
- +24h snapshot / source:
- +7d snapshot / source:
- Qualified engineering discussion (non-identifying count):
- Qualified GitHub/website/referral signal and limitations:
- Owner hours spent:
- Single testable next hypothesis: