Cobweb

Podcast 2 — In conversation

Speaker A: The new house had cobwebs in every corner of the loft. Clearly hadn't been touched in years.

Speaker B: Cobwebs in the loft are almost a universal feature of old houses. They're the sign that the previous owners never went up there.

Speaker A: I went for a long walk this morning specifically to blow away the cobwebs.

Speaker B: Blow away the cobwebs — clear your head with fresh air and movement. It's one of those idioms that perfectly describes the physical sensation.

Speaker A: The company website is a complete cobweb site. The last news post is from 2019.

Speaker B: A cobweb site — web jargon for a site left alive but completely neglected. Still technically online but as abandoned as an attic.

Speaker A: People sometimes confuse cobweb and cobweb pattern.

Speaker B: A cobweb refers to the actual structure. A cobweb pattern describes the radial, geometric design — the circular web with radiating spokes — used in knitting, crochet, and decorative arts. The pattern is beautiful; the cobweb in the corner is not.

Speaker A: And don't confuse cobweb with gossamer. Gossamer describes very fine, delicate fabric or anything extremely light and translucent — often used poetically. Cobweb can be used similarly — cobweb-fine silk, gossamer-thin glass — but gossamer is more elevated and literary. Cobweb stays earthier and more domestic.

Podcast 3 — Prompt engineering

Speaker B: Scenario one — a dependency audit prompt.

Audit this codebase for cobweb dependencies — packages that are still referenced in package.json but have not been updated in over two years, have known security vulnerabilities that were never patched, or are no longer maintained by their authors. For each cobweb dependency: show the last update date, vulnerability status, and recommend either upgrade, replace with an actively maintained alternative, or remove if unused.

Speaker B: Cobweb dependency is the exact metaphor for an abandoned package still clinging to the project like a dusty web in a corner.

Speaker A: Last update date plus vulnerability status gives the cobweb dependency audit both a staleness signal and a risk signal.

Speaker B: Next — a content audit prompt.

Run a cobweb site audit on this organisation's web presence. Identify pages that have not been updated in over 18 months, links that lead to 404 errors, content referencing products or services no longer offered, staff profiles for people who have left, and events or news items more than two years old. Generate a prioritised list of cobweb content to update, archive, or remove.

Speaker A: Staff profiles for people who have left are the cobweb content that damages trust most — a visitor contacting a departed employee.

Speaker B: Right. Now a database schema.

Create a PostgreSQL schema for a web content lifecycle management system that flags cobweb content. Tables: pages, content_blocks, audit_logs, cobweb_flags. cobweb_flags stores page_id, last_reviewed_date, last_updated_date, cobweb_reason enum stale_content, broken_links, outdated_references, departed_staff, discontinued_product, flagged_by enum automated_scan, manual_review, and resolution_status enum open, in_review, resolved.

Speaker A: Cobweb_reason enum with six distinct causes gives the content team specific information about why each page was flagged.

Speaker B: Fourth — a network security prompt.

Design a cobweb detection scan for network infrastructure. A cobweb asset is defined as: a server, service, or endpoint that has had no legitimate traffic in over 90 days but remains active and exposed. The scan identifies cobweb assets, checks their patch status, assesses their attack surface, and recommends: decommission, firewall-restrict, or document as intentionally dormant. Output as a risk-ranked cobweb asset report.

Speaker B: Cobweb assets with no traffic but still exposed are the attack surface risk that appears on every security audit but is rarely prioritised.

Speaker B: Fifth — a literary description prompt.

Write three atmospheric 60-word descriptions of cobweb settings for a gothic fiction writing assistant. Setting one: a Victorian greenhouse abandoned for thirty years. Setting two: a derelict church vestry. Setting three: an attic above a seaside guest house closed since 1987. Each description should use cobweb as a sensory and atmospheric detail — not just visual, but tactile and evocative of the specific history of that space.

Speaker A: Cobweb as tactile and evocative rather than purely visual expands the descriptive range beyond the obvious visual cliché.

Speaker B: Sixth — a full small app.

Build a single-page web app called Cobweb Cleaner for developers. User enters a list of npm packages with their last-updated dates and whether they are actively used. The app calculates a cobweb score per package based on days since last update and usage status, displays packages sorted from most cobwebbed to least, and suggests action from keep_active through monitor through replace through remove. All logic in vanilla JavaScript.

Speaker A: Cobweb Cleaner with a cobweb score per package makes dependency hygiene concrete and comparable.

Speaker B: That's the lesson — cobweb means neglected, abandoned, and entangled by time. In technical prompts, it names the class of things that should have been removed, updated, or decommissioned but weren't. The cobweb audit is the process of clearing what accumulated while no one was watching.

Speaker B: Prompt example: