Autobiography

Podcast 2 — In conversation

Speaker A: I am editing a manuscript and the author keeps using autobiography and memoir interchangeably. I want to explain to her why they are different. Can you walk me through the distinction?

Speaker B: Certainly. The distinction is primarily one of scope. An autobiography typically covers a whole life — or at least a substantial portion of it, from early childhood to the time of writing. It tends to follow a chronological arc and aims for comprehensiveness. Memoir, by contrast, is selective. It focuses on a specific period, theme, relationship, or experience and explores that in depth.

Speaker A: So if she is writing about her thirty years as a foreign correspondent, that is memoir, not autobiography?

Speaker B: Most likely, yes. Thirty years in a specific professional context, even if it touches on personal life, reads as memoir. If she begins with her childhood and traces how she arrived at foreign correspondence and then covers the career and its aftermath, that moves closer to autobiography. The test is whether the whole self across time is the subject, or whether a particular dimension or episode is the subject.

Speaker A: She also has a chapter written by a colleague who covered one of the same conflicts. Would that break the autobiography form?

Speaker B: That is more of an editorial decision than a definitional one. Strict autobiography is single-authored — the subject writing their own account. Incorporating another voice would technically move the work into hybrid territory. Some editors would classify such a book as a memoir with documentary sections, or simply as narrative nonfiction.

Speaker A: What about ghostwritten autobiography? Is that still an autobiography if someone else wrote it?

Speaker B: By convention, yes. The named person is considered the author in the commercial and publishing sense even when a ghostwriter did the actual writing. The ghostwriter is typically acknowledged somewhere in the book, on the copyright page or occasionally in an author's note. The autobiography genre tolerates this arrangement because the subject's life and testimony remain the material, even if the prose is someone else's.

Speaker A: I suppose the word is autobiography not authobiography.

Speaker B: Well observed. Autos in Greek means self. The self is the subject and the authority. Whether the prose was composed by that self or by a hired craftsperson is a secondary question about the production of the text, not its subject matter. The autobiography remains self-authored in the sense that the life and its account originate with the named person.

Speaker A: That helps. I will advise her that what she has is a memoir with autobiographical sweep.

Speaker B: That is a good formulation. Memoir with autobiographical sweep suggests depth of self-reflection and broad temporal range without claiming the exhaustive life-coverage that autobiography implies. Agents and publishers will know exactly what category they are reading.

Podcast 3 — Prompt engineering

Speaker B: Today we are working with autobiography. In development, this word comes up in the context of personal profile builders, author platforms, life-story applications, and content management tools for structured self-narrative. It is a rich prompt keyword. Let me walk through the prompts.

Speaker A: Personal narrative is a growth area in digital products — people documenting their lives, careers, and legacies online.

Speaker B: Exactly. And autobiography as a keyword signals structured, long-form, self-authored narrative — which is a specific and buildable product category. Here is a personal profile builder.

Speaker B: Build a personal profile builder where users write their own professional autobiography in structured sections. Sections include: Early Life and Background; Education and Formative Experiences; Career Journey with timeline entries each containing a role, organisation, date range, and a rich-text description; Major Achievements; Values and Philosophy; and a Current Focus section. Each section has a character guide (minimum and maximum word count displayed as a meter). Export to PDF and to plain HTML. Vanilla JavaScript, local storage, clean professional UI.

Speaker B: The character guide displayed as a meter is important. Autobiography has a natural minimum — too short and it is a bio, not an autobiography. Showing users how much they have written relative to a recommended range encourages the depth that makes the form meaningful. The export to both PDF and plain HTML gives immediate professional utility.

Speaker A: The section structure is essentially a template for the autobiography form. You are prompting for the scaffolding that an editor would normally provide.

Speaker B: Exactly. Prompting the sections explicitly means the AI builds them rather than producing a freeform text area. Here is a PostgreSQL schema.

Speaker B: Design a PostgreSQL schema for an author and biography management system. Include: an authors table with id, full_name, pen_name nullable, birth_date, nationality, and bio_type enum with values autobiography, memoir, biography, and mixed; a books table with id, author_id referencing authors, title, publication_year, word_count, and ghostwriter_name nullable; a timeline_events table with id, author_id, event_year, event_title, event_description, and category enum with values personal, professional, and historical_context; and a themes table with id, book_id, theme_label, and prominence_score integer 1 to 5. Add foreign keys and indexes on author_id.

Speaker B: The bio_type enum with autobiography as one of the values is the autobiography-specific element. The ghostwriter_name nullable column acknowledges the commercial reality of the form. The timeline_events table with a historical_context category allows events to be placed against their era, which is how the best autobiographies contextualise personal experience.

Speaker A: The themes table with prominence score is interesting — it treats autobiography as analysable text, not just narrative.

Speaker B: It does. Useful for a reading platform or academic database. Here is a life events timeline visualisation.

Speaker B: Build a life events timeline visualisation component as an inline SVG rendered by JavaScript. Data source is a JSON array of objects each with year, label, category as personal or career or education, and optionally a description. Render as a horizontal timeline with decade markers, colour-coded dots per category, and a tooltip on hover or tap showing year, label, and description. The timeline should be scrollable horizontally on small screens. No external libraries, vanilla JavaScript.

Speaker B: SVG rendered by JavaScript means the component is embeddable in any autobiography platform with no external dependencies. Decade markers give temporal structure — important for an autobiography that spans decades. Category colour-coding gives the reader an instant visual sense of the balance between personal and professional life across time.

Speaker A: You can see at a glance whether someone's story is dominated by career or by personal experience.

Speaker B: A revealing visualisation. Here is a ghost-writing project management prompt.

Speaker B: Build a ghost-writing project management app for autobiography projects. Features: a projects list where each project has an author client name, a target word count, a deadline, and a status of discovery, drafting, review, or final; a chapters panel per project showing chapter title, assigned section from the autobiography template such as early life or career, word count target, current word count, and status of not-started, in-progress, or complete; a sessions log where each session has a date, duration in minutes, session type of interview or writing or revision, and notes; and a progress dashboard showing overall word count, percentage complete, and days to deadline. Vanilla JavaScript, local storage.

Speaker B: The sessions log with session type interview, writing, revision captures the actual workflow of ghostwriting an autobiography. Discovery interviews with the subject come first, then writing, then revision rounds with the subject reviewing for accuracy and voice. Structuring the app around this workflow makes it genuinely useful for professional ghostwriters.

Speaker A: And the chapter section mapping to the autobiography template — early life, career — links the tool directly back to the form's structure.

Speaker B: All the moving parts are connected. Here is the full platform prompt.

Speaker B: Build a full autobiography publishing platform. Features: a public reader view where approved autobiography chapters appear as paginated, typographically clean reading pages; an author writing dashboard where the subject or ghostwriter drafts and edits chapters in a rich text editor with autosave; an editorial workflow dashboard where an editor can leave inline comments on specific paragraphs, mark chapters as approved or requiring revision, and track overall completion status; a timeline page generated automatically from tagged events in the text; and an about the author panel showing a brief third-person bio beside the autobiography. Vanilla JavaScript, local storage, responsive design.

Speaker B: The automatically generated timeline page is the most technically ambitious element. It requires the platform to parse tagged events from the prose — a lightweight structured-markup approach where the author tags year and event inline and the platform aggregates them into the timeline component we built in the earlier prompt. Describing it as generated automatically in the prompt makes the AI build the parsing logic rather than a manually populated timeline.

Speaker A: Linking the two prompts together — the timeline component and this platform — would give a complete system.

Speaker B: That is the right way to think about prompt engineering for complex products. Build modular components with individual prompts, then compose them into a platform with a single integrating prompt that describes how they connect. Autobiography as the subject matter provides a consistent structural metaphor — chapters, timeline, narrative arc — that unifies the entire system.