Writing Literary Tech Prose

Given a topic or raw material (a memory, a technical concept, a person's biography, an occasion), identify:

1. Form — essay, memoir, science-pop article, fanfiction, poem, letter, manifesto, or portrait
2. Audience — specialist publication, general public, a specific person, or personal archive
3. Core tension — the idea/feeling/contrast that makes it worth reading (not just informative)

Then draft using the form-specific workflow below. Always lead with a concrete image, scene, or question — never with a dry thesis statement.

Progress:

• Clarify form and audience
• Find the "hook" — a concrete detail, anecdote, or paradox
• Build structure appropriate to form (see below)
• Draft with voice consistent to form
• Revise for rhythm, precision, and emotional landing
• Check factual/technical accuracy if engineering content is involved

Form-specific structures

Essay / column (публицистика):

• Open with a specific scene, question, or provocative claim
• Weave technical/cultural/philosophical threads together — don't silo them
• Build toward a turn or insight, not a summary
• End on an image or open question, not a flat conclusion

Technical memoir (мемуары):

• Anchor in sensory/concrete detail (the smell of a workshop, a specific error message, a colleague's phrase)
• Organize chronologically or thematically around a project/team/trip
• Let technical detail serve emotional truth, not vice versa
• Include failure and ambiguity — avoid hagiography

Science-pop article (научпоп):

• Start with a vivid real-world phenomenon or question ("Why does a bumblebee seem aerodynamically impossible?")
• Use analogy to bridge unfamiliar concept to familiar experience
• Introduce technical terms only after the intuition is built
• Close the loop back to the opening phenomenon with the now-explained mechanism

Fanfiction / alt-history (альтернативная история):

• Establish the point of divergence or the borrowed world explicitly early
• Respect internal logic of the source world or technology
• Use "what if" as structural engine, not decoration
• Ground speculative elements in plausible technical/social consequences

Technical poetry (поэзия):

• Use precise engineering vocabulary as the primary poetic material (not metaphor layered on top)
• Exploit rhythm of technical terms (stress patterns, foreign-root words) for sonic effect
• Let mechanism/process become metaphor for human experience (flight, fatigue, pressure, tolerance)
• Avoid clichés ("steel wings of freedom") — seek the unexpected technical-emotional pairing

Letters (эпистолярия):

• Match register to occasion and recipient (formal gratitude vs. intimate congratulation)
• Open with a specific, personal detail — never a generic greeting
• One clear emotional/thematic core per letter
• Close with a gesture, not a summary

Manifestos (манифесты):

• State principles as imperatives or declarations, not arguments
• Use repetition and parallel structure for rhetorical force
• Be willing to be one-sided and provocative — manifestos are not balanced essays
• Keep it short; density of conviction matters more than length

Biographical portraits (биографии):

• Lead with a defining scene or anecdote, not birth-to-death chronology
• Select 2-3 traits/episodes that reveal character, rather than cataloguing achievements
• Include contradictions or lesser-known sides
• Situate the person in their technical/historical context without turning it into a textbook entry

Example 1: Input: Write a science-pop piece on why airplane wings generate lift. Output: Opens with the common myth (equal transit time) and a disorienting fact (it's wrong), builds intuition via a hand-out-the-car-window analogy, introduces Newton's third law and pressure differential conversationally, ties back to how pilots actually feel lift during takeoff.

Example 2: Input: Turn a memory of a failed rocket test into a memoir chapter. Output: Opens mid-scene — the countdown, a specific gauge reading, the silence after the anomaly — then pulls back to context (the team, the stakes), interweaves technical cause with human reaction (blame, exhaustion, dark humor), closes on what changed afterward, not on a moral.

Example 3: Input: Write a short technical poem about metal fatigue. Output: Uses terms like "cyclic load," "crack propagation," "yield point" as the poem's actual vocabulary, mapping them onto aging, memory, or love without ever naming the metaphor directly.