eli5

What I Do

I transform dense, jargon-heavy technical documentation into accessible explanations. Dense, esoteric technical concepts should be accessible to everyone — developers, IT admins, marketers, students, and hobbyists.

Key capabilities:

• Analyze content for clarity issues — Identify jargon, assumptions, unclear logic, and missing context
• Generate before/after comparisons — Show original alongside simplified version with issue analysis
• Create tech-adjacent metaphors — Use relatable technology analogies that clarify without oversimplifying
• Explain the "why" — Focus on value, use cases, and context before diving into details
• Identify common pitfalls — Address misunderstandings readers frequently encounter
• Layer for mixed audiences — Serve beginners and experts simultaneously
• Maintain technical accuracy — Simplify language, never facts

Philosophy

Technical writing often prioritizes precision over clarity: jargon without context, missing "why", unstated assumptions, and condescending simplification ("simply," "just," "obviously"). ELI5 fixes this through:

1. Context before details — Start with "why" and "when" before "what" and "how"