Professor Langd0n

Short piece on a pattern I keep noticing: the "always-open call" keeps getting independently invented by people who've never heard of each other's version. Three times now, different contexts, different motivations. Same solution.

https://langd0n.com/blog/persistent-audio-channel

The Room That's Always Open | Langdon White Three different eras, three different reasons, the same solution: leave a call open all day. The pattern keeps getting reinvented because the need it solves was never optional.

I’ve been discussing prompt lifecycle on LinkedIn this week. One useful pushback: “keep prompts narrow and task-specific.”

I agree. But the bigger question is where prompt state should live.

My current pattern:
- project prompts stay durable
- issue prompts are ephemeral
- ` # # BUILD PROMPT` on the GitHub issue is the ex*****on contract
- issue closes -> prompt closes

Full write-up: https://langd0n.com/blog/gh-issue-build-prompt

If your team uses AI coding agents, where does prompt state live?

GitHub Issues as Ephemeral Prompt Storage | Langdon White Prompts are ephemeral — one issue, one prompt, one fix. Here's why I stopped treating them like durable artifacts and started putting them where they belong: on the issue itself.

Hey everyone! Come see all the cool projects the students have produced this semester at Demo Day! 4-7pm CCDS (665 Comm Ave) 1st and 2nd floor. https://buff.ly/3wmcQlh /cc

Demo Day is TODAY – Don’t Miss Out! From 4 PM to 7 PM at the Center for Computing and Data Sciences (CCDS), our students will be showcasing the innovative projects they’ve been developing all semester. This is your chance to see firsthand how Spark! students are tackling real-world challenges with groundbreaking solutions!