[Anchor Proposal]: YOLO

[mikrobe]

Proposed Term

YOLO

Context (Optional)

No response

Pre-submission Checklist

• I have searched existing anchors and this term is not already included
• This term refers to a well-established concept (not something I invented)

[raifdmueller]

Evaluation against Quality Criteria

Criterion	Score	Assessment
Precise	❌	"YOLO" has no clear boundaries. It could mean "You Only Look Once" (a computer vision architecture by Redmon et al., 2016), or the colloquial "You Only Live Once" (a lifestyle motto). Neither is a methodology with actionable structure.
Rich	❌	Does not activate multiple interconnected concepts. As slang, it's a one-dimensional sentiment. As a CV model, it's highly specific but not a development methodology.
Consistent	❌	Different users invoking "YOLO" would get wildly different conceptual activation — some LLMs would produce computer vision code, others motivational text.
Attributable	⚠️	If CV: Joseph Redmon (2016). If slang: no authoritative source.

Recommendation

Reject. "YOLO" fails three of four quality criteria. It is either:

1. A computer vision architecture — too narrow and domain-specific for this catalog
2. A lifestyle motto — a pure instruction without conceptual depth (same category as "TLDR" or "Keep it short", which are explicitly listed as counter-examples in our quality criteria)

No context was provided to clarify which meaning was intended, which itself demonstrates the consistency problem.

[raifdmueller]

Revised Evaluation — YOLO as Vibe Coding Disposition

My initial assessment missed the relevant context. In the vibe coding community, "YOLO" (You Only Live Once) has a specific, established meaning:

Skip all safety checks and move at maximum speed. Equivalent to --dangerously-skip-permissions, no tests, no reviews, no spec — just prompt and ship.

Revised Quality Criteria

Criterion	Score	Assessment
Precise	✅	In the coding context, "YOLO mode" has clear boundaries: skip permissions, skip tests, skip reviews, accept all risk for speed. Developers know what it means.
Rich	✅	Activates a disposition (like WWCND): risk acceptance, speed over safety, no guardrails. Also activates awareness of what is being skipped — an LLM asked to work in "YOLO mode" understands it is operating without the safety net.
Consistent	✅	In the developer/vibe-coding context, YOLO is consistently understood. The computer vision meaning (Redmon, 2016) is a separate domain and would only activate with explicit ML/CV context.
Attributable	⚠️	No formal methodology publication. But the term is densely present in developer culture, conference talks, and LLM training data. Similar attribution level to WWCND before its formal validation.

Relationship to Existing Anchors

• WWCND — Sibling. WWCND activates decisiveness and commitment (pick the most direct solution). YOLO activates risk acceptance (skip the safety checks). WWCND can still produce a careful solution if that's the most direct one; YOLO explicitly skips safeguards.
• Vibe Coding Risk Radar — YOLO is the opposite end of the spectrum from the Risk Radar's tiered mitigations.

Revised Recommendation

Accept as Tier ★★☆ (Needs qualification). In bare form, it risks the CV interpretation. With a qualifier like "YOLO mode — skip all safety checks" or framed within the vibe coding context, it activates reliably.

Could be a valuable anchor precisely because it names the anti-pattern explicitly — an LLM told "we are NOT in YOLO mode" understands what safety checks to enforce.