Příručka junior.guru

Voice

• Write in Czech.
• Address reader using informal second-person singular: ty, tebe, tvoje, and imperative verbs. Use formal address only inside quotes or source material.
• Assume reader is smart but new to topic. Explain context and jargon instead of assuming insider knowledge.
• Keep tone warm, human, practical, and experienced. Avoid fluffy encouragement, academic prose, and corporate marketing language.
• Treat facts, risks, tradeoffs, red flags, and job-market reality seriously. Debunk myths and state unpleasant truths directly when useful.
• Be empathetic without patronizing. Acknowledge difficult beginnings without infantilizing reader.
• Use occasional vivid comparison, light joke, or colloquial phrase when it aids understanding, never when it weakens advice.

Advice

• Avoid absolute claims and universal prescriptions. Prefer contextual wording such as často, většinou, může, záleží, and pro tebe, with reasons.
• Stay independent and non-salesy. Reduce confusion and decision paralysis; do not push one course, product, or supposedly correct life path.
• Curate instead of exhausting topic. Prefer few strong recommendations with explanations over large link dumps.
• Make advice concrete and actionable: what to do, why, what to expect, and what can go wrong.
• Rewrite rough community notes into polished prose with correct grammar, spelling, and punctuation.

Inclusion

• Push back against elitism, sexism, ageism, and other gatekeeping about who belongs in IT.
• Prefer inclusive wording; avoid unnecessary generic masculine forms. Use direct second person, neutral plurals, or paired forms such as vývojářka nebo vývojář where practical.
• Do not assume reader's gender, age, family situation, education, health, or background unless page specifically addresses that group.
• When gendered wording is unavoidable, use it deliberately and sparingly rather than mechanically defaulting to masculine forms.

Structure and style

• Use mostly short-to-medium, clear, direct sentences. Give important claims their own sentence when helpful.
• Open with clear promise, often using short lead made of punchy sentences or questions.
• Organize practical content under descriptive headings.
• Use lists for steps, options, requirements, myths, tradeoffs, or checklists. Keep them concrete and scannable.
• Bold key takeaways, not decorative phrases.
• Link relevant handbook chapters instead of repeating their content.
• Make English IT terms clear from context or explain them in Czech.
• Spell brand exactly junior.guru in running text. Prefer klub junior.guru and podcast junior.guru. Use Junior Guru only when dot cannot be used.