Brainwave

Podcast 2 — In conversation

Speaker A: I had a brainwave yesterday — wedging lemon behind the radiator so the hall smells vaguely Mediterranean.

Speaker B: That is either genius or a fire officer’s headache. I use brainwave for instant fixes, not slow plans.

Speaker A: Example that felt legit?

Speaker B: She had a brainwave and routed cables through the skirting — saved us drilling the brick.

Speaker A: Is it interchangeable with Eureka?

Speaker B: Similar punch, but Eureka wears a lab coat — brainwave sounds like slippers and tea.

Speaker A: And inspiration?

Speaker B: Inspiration is broad weather. Brainwave is one lightning strike you can practically date.

Speaker A: Mistakes?

Speaker B: Overusing it in meetings — not every brainstorm output is a brainwave. Saves credibility if you ration the word.

Speaker A: What about strike of genius?

Speaker B: Louder applause. Stroke of genius is similar. Brainwave stays modest, friendly, slightly witty.

Speaker A: American cousin?

Speaker B: They might simply say idea or light-bulb moment — brainwave travels best on this side of the Atlantic.

Speaker A: Brilliant. Brainwave unlocked — now I owe you a biscuit for the cabling tip.

Podcast 3 — Prompt engineering

Speaker B: In prompts, brainwave cues the model to capture sudden ideas with structure — timestamps, rationale, backlog placement.

Speaker A: UI prompt first?

Speaker B: Feature panel brainstorm:

Prompt: Design an engineering wiki side panel labelled Brainwave inbox where teammates pin spur-of-the-moment ideas tagged by component. Include quick filters by stack, pastel priority chips, markdown preview, keyboard shortcut to stash a brainwave mid-meeting without leaving the IDE theme.

Speaker A: Forces humane capture UX.

Speaker B: Top navigation riff:

Prompt: Build a SaaS navbar with anchors for roadmap, backlog, and brainwave log. Hover states should subtly animate like a filament warming up. Respect WCAG AA, include iconography hinting sparks, never bury the newest brainwave below marketing banners.

Speaker B: Persist those sparks responsibly:

Prompt: Design a Postgres schema tracking brainwave entries linking to repos, Slack threads, and experiment outcomes. Provide partial indexes by team_id and created_at so retro meetings list last week’s flashes fast, storing JSON metadata for feasibility votes.

Speaker A: HR-friendly flow?

Speaker B: Yes — celebrate micro-innovations:

Prompt: Create an HR web form where staff submit a quarterly brainwave that improved onboarding. Validation must forbid empty praise, attachments optional, anonymity toggle for shy engineers, exporting CSV for managers with readable timestamps and department tags.

Speaker B: Finance dashboard twist:

Prompt: Prototype an accounting dashboard showing how a billing brainwave cut DSO — include line chart versus prior quarter, annotation callouts explaining the idea, CSV export, colour tokens that remain legible when finance shares screens in bright offices.

Speaker A: Greenfield builds?

Speaker B: Tight brief, big leverage:

Prompt: From four bullet requirements, scaffold a progressive web app for field technicians to log onsite brainwaves about faulty hardware. Offline queue, conflict resolution notes, minimal dependencies, rationale comments before sync, and Lighthouse budget guardrails spelled out explicitly.

Speaker B: Last — design system guardrails:

Prompt: Draft CSS custom properties for a joyful yet serious design system celebrating brainwave moments — electric yellow accents, softened night mode, elevation tokens that pop modals announcing new ideas. Document motion curves that respect prefers-reduced-motion yet still acknowledge celebratory flashes.

Speaker A: Brainwave tells the model this is lightning, not backlog noise.

Speaker B: Exactly — you are scripting how serendipity gets logged, reviewed, shipped.