Cemetery

Podcast 2 — In conversation

Speaker A: I went to Highgate Cemetery in London last weekend. I had never been before. It was quite extraordinary — not at all what I expected.

Speaker B: Highgate is remarkable. The Victorian section in particular. What surprised you about it?

Speaker A: How beautiful it was, honestly. I had this image of a cemetery as a rather bleak, quiet place. But Highgate is genuinely atmospheric — ivy-covered tombs, stone angels, winding paths through overgrown trees. It felt more like a wild garden than a burial ground.

Speaker B: That was entirely intentional. The garden cemetery movement in the nineteenth century was a response to overcrowded city churchyards. The idea was to create dignified, parklike spaces — almost landscaped retreats — where the living could visit and reflect. Cemetery comes from the Greek for sleeping place, which gives you a sense of the tone they were aiming for.

Speaker A: I did not know that. So cemetery and graveyard are not interchangeable?

Speaker B: Not really, no. Graveyard tends to refer specifically to the burial ground around a church — it is older and more rural in feel. Cemetery usually refers to a larger, formally planned burial site, often unattached to a church. In everyday speech people use them interchangeably, but technically they are different things.

Speaker A: What about memorial park? I have seen that on some newer sites.

Speaker B: That is the modern euphemism, popular in America and increasingly here too. It softens the associations — park sounds welcoming, memorial sounds respectful, and together they sidestep the word death almost entirely. Cemetery is more honest in that sense. It does not try to disguise what it is.

Speaker A: You would say "I visited the cemetery" but probably not "I visited the memorial park" in normal conversation.

Speaker B: Exactly. Cemetery is the natural, neutral choice in standard British English. It works in formal writing, news reporting, literature, and everyday speech without sounding either clinical or morbid. Graveyard has slightly more Gothic flavour — useful if you want that atmosphere in writing, but possibly too heavy for a straightforward factual context.

Speaker A: And in figurative use? I have heard people say "a cemetery of ideas" or that kind of thing.

Speaker B: Yes, it works figuratively for things that are dead and buried — abandoned projects, extinct companies, forgotten movements. "The cemetery of failed startups" or "a cemetery of unfinished novels." It always carries that sense of finality and silence. You would not use it lightly.

Podcast 3 — Prompt engineering

Speaker B: Today we are looking at cemetery in prompt engineering. It is a word with a strong thematic identity — burial, memory, finality, historical record — and that identity makes it genuinely useful when you need to anchor an AI in a specific domain context for development work.

Speaker A: The figurative uses seem interesting too. "A cemetery of deprecated endpoints" or "a cemetery of legacy modules" — that kind of framing could be useful in architecture prompts.

Speaker B: Exactly right. Let us begin with a heritage and tourism application, which is the most direct use case.

Speaker B: PROMPT 1: Build a cemetery heritage and visitor management web application for a Victorian cemetery trust. Include an interactive map with clickable burial plots, a searchable database of interments with name, date of birth, date of death, and biography, a guided tour module with GPS waypoints and audio descriptions, a volunteer management system, and an admin panel for records entry and map editing. Stack: React, Node.js, PostgreSQL with PostGIS for geospatial queries.

Speaker A: The PostGIS detail for the burial plot map is exactly right — spatial queries are essential for that kind of interactive map. That makes the prompt technically precise.

Speaker B: Now a genealogy research platform where cemetery records are central.

Speaker B: PROMPT 2: Design a PostgreSQL schema for a genealogy and cemetery records platform. Include tables for persons with birth and death dates, burial location, and biographical notes; cemetery sites with GPS coordinates, opening hours, and heritage status; plot records linking persons to specific burial plots; and user submissions for crowdsourced corrections. Add full-text search indexes on name and biography fields. Include a view joining persons to their cemetery and plot details.

Speaker A: The crowdsourced corrections table is a realistic touch — genealogy platforms rely heavily on community contributions to fix transcription errors in old records.

Speaker B: Now the figurative use — a legacy code audit dashboard.

Speaker B: PROMPT 3: Build a legacy code cemetery dashboard for a software engineering team. The dashboard should display deprecated modules, retired API endpoints, and decommissioned services — the "buried" parts of the codebase. Each entry should show the date retired, the reason, the replacement if any, and whether it has been fully removed or is still lingering. Include a search filter, status badges, and a timeline chart of retirements per quarter. Stack: Vue.js with a JSON file backend.

Speaker A: That is a genuinely useful tool. Every large codebase has a graveyard of old endpoints that nobody has fully cleaned up. Framing it as a cemetery makes the purpose immediately clear to the AI.

Speaker B: Here is one for a memorial and funeral services business management system.

Speaker B: PROMPT 4: Build a business management system for a cemetery and funeral services company. Include client case management from first contact through burial, plot inventory with availability status and GPS coordinates, invoice and payment tracking, a scheduling calendar for services and groundskeeping, staff assignment, and a reporting dashboard with monthly interment statistics. Stack: Angular, Express REST API, PostgreSQL.

Speaker A: The groundskeeping scheduling alongside client services scheduling shows the AI that this is a real operational system, not just a records database. That level of domain detail matters.

Speaker B: Now a public-facing memorial website builder.

Speaker B: PROMPT 5: Create a memorial website builder that allows families to create a dedicated online memorial page for a deceased person. Each page should include a photo gallery, a biography section, a guestbook for tributes, a private family section with password protection, and social sharing. Include an admin panel for the funeral home to manage client pages. Stack: Next.js with Supabase for auth and storage, Tailwind CSS.

Speaker A: The private family section with password protection is a feature that real memorial platforms offer. Including it shows contextual awareness of what families actually need.

Speaker B: One more — a mobile app for cemetery visitors.

Speaker B: PROMPT 6: Design a React Native mobile app for cemetery visitors. Features: an interactive GPS map of burial plots with search by name or date; an augmented reality mode that overlays the deceased person's name and dates when the phone camera is pointed at a headstone; push notifications for upcoming memorial dates; and an offline mode for areas with poor signal. Include a backend API in Node.js and a PostgreSQL database of cemetery records.

Speaker A: The augmented reality overlay on headstones is a feature that actually exists in some heritage apps. Including it in the prompt gives the AI a genuinely innovative but realistic feature to implement.

Speaker B: And finally, the figurative use in a software architecture context.

Speaker B: PROMPT 7: Create a microservices decommissioning tracker — a "software cemetery" — for a large engineering organisation. Track services that have been sunset, with metadata including original purpose, date deployed, date retired, owning team, replacement service, and any lingering dependencies. Provide a REST API for querying the registry, a dashboard for engineers to browse and search retired services, and a webhook that notifies a Slack channel when a new service is added to the cemetery. Stack: Node.js, PostgreSQL, React dashboard.

Speaker A: A Slack webhook notification when something is added to the software cemetery is a clever detail. It keeps the team aware of what is being decommissioned in real time.

Speaker B: That is the range of cemetery in prompt engineering. Use it in its literal sense and you unlock a rich domain — heritage, genealogy, memorialisation, tourism, and funeral services — each of which demands specific data models and real workflows. Use it figuratively and you get a powerful framing for legacy systems, deprecated code, and technical debt. Either way, it gives the AI precise context and sharper output.