Copy

Podcast 2 — In conversation

Speaker A: The marketing copy for the landing page needs a complete rewrite. It reads like it was written for us, not for the customer.

Speaker B: Marketing copy as customer-facing text — the written content of an advertisement or landing page. Customer-centred copy focuses on the reader's benefit, problem, and motivation, not the company's achievements. Copy that talks about we and our tends to be less effective than copy that leads with you and your.

Speaker A: Could you send me a copy of the report before the meeting? I want to review the figures in advance.

Speaker B: A copy of the report — one reproduction of the document, whether physical or digital. In this context the word is entirely neutral — just asking for the document to be sent. The abundance of copying in the digital world means we barely notice it.

Speaker A: She copied the design from a competitor almost exactly. It's remarkable how brazen it was.

Speaker B: Copy as imitation — reproducing another's work without authorisation or originality. In design and in code, copying someone else's work can cross the line from inspiration to infringement. The question is always how much was taken and whether it was protected.

Speaker A: People sometimes confuse copy and duplicate.

Speaker B: A duplicate is an exact replica — identical in every detail, often created deliberately for backup or redundancy purposes. A copy is broader: it can be an imperfect reproduction, a photocopy that has degraded slightly, or a manuscript copy with occasional errors. In digital contexts they are often used interchangeably, but duplicate implies precision — exact match — where copy allows for approximate reproduction.

Speaker A: And in email, don't confuse copy and blind carbon copy. When you copy someone — add them to CC — all recipients see they were included. When you blind carbon copy someone — BCC — only the sender and the blind-copied recipient know they received the message. Using BCC for transparency can be seen as duplicitous; using CC when BCC was intended can expose a recipient's inclusion inappropriately.

Podcast 3 — Prompt engineering

Speaker B: Scenario one — a copywriting prompt.

Write conversion-focused copy for a SaaS project management tool's landing page hero section. The copy must: lead with the customer's primary pain point (projects going over schedule and over budget due to poor visibility), show the product as the solution in one sentence without feature-listing, include a specific, credible social proof element, and end with a call to action that creates mild urgency without false scarcity. The copy should be scannable on mobile, with a headline under 10 words, a subheadline under 20 words, and a CTA button label under 5 words.

Speaker B: Headline under 10 words, subheadline under 20, CTA under 5 — these copy length constraints are the discipline that forces clarity and prevents the filler that dilutes conversion copy.

Speaker A: Leading with the customer's pain point rather than the product's features is the copy inversion that makes landing pages convert — the reader recognises their problem, then discovers the solution.

Speaker B: Next — a file copy system prompt.

Design a robust file copy service for a document management platform. The service handles large file copies (up to 10GB) with: chunked streaming copy that avoids loading the entire file into memory, a checksum comparison after copy to verify the copy is identical to the source, progress reporting via a status endpoint that clients can poll, automatic retry on transient failures, and a copy log that records source path, destination path, copy start time, copy end time, file size, and whether the checksum verified successfully. Failed copies are logged with the error and the last successful chunk position for potential resume.

Speaker A: Last successful chunk position on failed copies enables resume rather than restart — for a 10GB file, resuming from chunk 8GB is significantly better than starting over.

Speaker B: Right. Now a database schema.

Create a PostgreSQL schema for a digital asset copy and version management platform. Tables: assets, asset_copies, copy_permissions, version_history, distribution_records. asset_copies stores asset_id, copy_type enum master, working_copy, distribution_copy, backup, created_from_copy_id nullable, created_at, storage_path, file_size_bytes, checksum, and copy_status enum active, archived, deleted. copy_permissions stores asset_id, user_id, permission_type enum view, copy, distribute, and granted_by. distribution_records stores copy_id, distributed_to, distribution_date, distribution_method, and copy_restrictions text describing any conditions on the distributed copy.

Speaker B: Copy_type distinguishing master, working copy, distribution copy, and backup is the asset management hierarchy that controls which copy can be further copied, modified, or distributed.

Speaker B: Fourth — an AI content prompt.

Write a prompt engineering guide for using AI to assist with advertising copy. Cover: how to brief the AI on the target audience (demographics, pain points, and language they use), how to specify the copy format and length constraints in the prompt, how to request multiple copy variants in a single prompt for A/B testing, how to prompt for copy that avoids common clichés (leverage, seamless, robust, game-changing), and how to iterate on AI-generated copy through structured feedback prompts (make it more direct, reduce the jargon, lead with the benefit not the feature).

Speaker A: Prompting to avoid specific clichés by listing them is more effective than asking for original copy in general — the AI can avoid specific words it is told to avoid more reliably than it can self-assess originality.

Speaker B: Fifth — a clipboard copy prompt.

Build a copy-to-clipboard utility component for a developer tools web app. The component: shows a code block with a copy button in the top-right corner, copies the code to the clipboard on click using the Clipboard API with a fallback for browsers that do not support it, shows a brief visual confirmation (button label changes from Copy to Copied with a tick icon) that reverts after 2 seconds, handles copy failure gracefully by showing an error state and suggesting the user manually select and copy the text, and preserves indentation and whitespace exactly in the copied text.

Speaker B: Preserving indentation and whitespace exactly in copied code is the developer experience requirement — losing indentation from copied code blocks forces developers to reformat before use.

Speaker B: Sixth — a full small app.

Build a single-page web app called Copy Vault — a personal clipboard history manager. The app stores up to 100 recent text copies that the user pastes into the vault manually (since direct clipboard monitoring is not available in standard web apps). Each entry is saved with a timestamp, an auto-detected category (code, URL, email, phone, or general text), and a user-editable label. User can search entries by content or category, pin important entries to the top, and copy any entry back to the clipboard with one click. All data in localStorage.

Speaker A: Auto-detected category from content analysis — URL pattern, phone number pattern, code syntax — reduces the manual tagging burden and makes the vault useful without the user having to label everything.

Speaker B: That's the lesson — copy is the abundance made material. The word comes from Latin copia — plenty — and the act of copying has been multiplying abundance ever since. The printing press made copying texts cheap. Digital technology made it free. The economics of the modern information world are entirely built on the zero marginal cost of digital copying — and the legal and business frameworks we build are attempts to manage what copying with no friction actually means.

Speaker B: Prompt example: