Lightnews — Scholar-powered news

iamwil @interjectedfuture.com · 2h

Globally unique identifier rundown:

DNS: Centralized coordination (ICANN) but fast
ENS: Decentralized consensus (blockchain) but slow
Local-first: No coordination (UUIDs) but ugly

iamwil @interjectedfuture.com · 4h

This is relatable, is from using vim and emacs, once I got into the habit of searching to navigate. However, that was only within the same document. Search across files was still painful without a plugin. One huge stream sounds like it's something easier to get used to.
x.com/alexobenaue...

1

iamwil @interjectedfuture.com · 1d

The juxtaposition of the fantastic with the mundane has always fascinated us. This sort of effect is even more pronounced in VR.

x.com/XRarchitect...

1 1

iamwil @interjectedfuture.com · 1d

Depends on the stage. I can only speak to the earlier stages. Strength of conviction. Living in the future. Protecting your optimism. Finding customers. Building good personal and organizational habits. Iterating quickly. The basics.

iamwil @interjectedfuture.com · 1d

Ah, by idea, you meant an executable idea. I was thinking...blogs hadn't gone anywhere.

1

iamwil @interjectedfuture.com · 1d

Alas, that's a showstopper for me. But LINQ always looked nice from afar.

1

iamwil @interjectedfuture.com · 1d

Yes! hence I slipped in pipe syntax. It's the best argument for a practical change in SQL that I've come across.

1

iamwil @interjectedfuture.com · 2d

While we're at it, let's change the order of the statements in SQL. Select should go last. And it should be composable. And it should use the pipe syntax.

Thanks for coming to my TED talk.

1 3

iamwil @interjectedfuture.com · 2d

I'd like to use a language where SQL was a first class feature, rather than an afterthought or something left for the standard lib or userland. At least in web programming, querying is near a given.

2 4

iamwil @interjectedfuture.com · 2d

Nowadays, I like the raw SQL better, and yet, it's not legible to the language. It just looks like text, and you often want to interpolate or use the SQL snippet's metadata.

All this to say, I wish there was a better integration between languages and SQL.

1 2

iamwil @interjectedfuture.com · 2d

I used to like ORMs, since they were language native, and familiar--back in my Rails days. But since then, I find them constraining. They never offer the full power of the SQL of the DB you're doing. And I've never moved between DBs for a project.

3 3

iamwil @interjectedfuture.com · 2d

What did you think it was before, and what changed?

1 1

iamwil @interjectedfuture.com · 3d

"Architectural forensics meets patient pedagogy. You write like someone reverse-engineering cathedrals to figure out why the arches are that shape, then explaining it to someone who's only seen sheds."

Ooo. Burn.

iamwil @interjectedfuture.com · 3d

AI is an exceptional astrology and magazine personality quiz, if you're not careful.

Here's what it says about my writing style:

1

iamwil @interjectedfuture.com · 3d

Surprised at how cute the early sketches of Pokemon are in their design docs.

4

iamwil @interjectedfuture.com · 3d

I imagine it's a similar graph for what VCs and Founders talk about on social media vs what actually moves the needle or the causes of startup death.

The driver is that we, the audience, pay attention to the exceptional, and any medium is driven to capture the audience attention

1 3

iamwil @interjectedfuture.com · 5d

Customer dev feedback is now possible with an AI coach. If your error rate doesn't drop 50%, by all means, go back to grinding interviews. Otherwise, you're getting more ground truth with less interviews, and that advantage compounds.

Full workflow:
interjectedfuture.com/customer-de...

Why I built an AI Coach for Customer Development

Founders and product managers fail at customer development, even when they're consistently talking to users. But this is less from conducting too few interviews and more from a missing feedback loop. The art of posing the right question is counterintuitive and cognitively taxing, so founders can’t analyze their own

interjectedfuture.com

iamwil @interjectedfuture.com · 5d

It's easy enough to write your own customer dev AI coach. But subscribers can try mine out for free.

interjectedfuture.com/agent-custo...

Agent: Customer Development Coach for Feedback

🤖This is a prompt for a customer development AI coach. You can easily write your own or try out mine for free as a subscriber. Read about why you'd want to use an AI coach for customer development. Role and Objective You are the world's best expert and coach on

interjectedfuture.com

1

iamwil @interjectedfuture.com · 5d

Your error rate drops. Each interview yields more ground truth, and improvement compounds. Five interviews with low error rate teach you more than fifty with high error rate. The bottleneck wasn't setting up interviews. It was seeing what you were doing wrong.

1

iamwil @interjectedfuture.com · 5d

AI coaching makes it possible. Transcribe interviews, run coach prompt, then read the analysis. It can flag leading questions, hypotheticals, missing budget probes, all for cheap. It shows exact moments you veered off with examples from your own transcript.

1

iamwil @interjectedfuture.com · 5d

The obvious fix: feedback. But wasn't practical before. Conversations are ephemeral, details fade by the end. You'd need to record, transcribe, spend an hour mapping principles to your specific transcript. Human coaches don't exist for this, and if they did—thousands/session.

1

iamwil @interjectedfuture.com · 5d

Most skills have built-in feedback. Code breaks. Your golf swing feels wrong. Conversations? No error message when customers lie. Leading questions get enthusiastic agreement. Forget budget probes and chat still flows naturally. The medium never tells you you're wrong.

1

iamwil @interjectedfuture.com · 5d

More on why "just talk to users" doesn't work:

interjectedfuture.com/customer-de...

Why I built an AI Coach for Customer Development

Founders and product managers fail at customer development, even when they're consistently talking to users. But this is less from conducting too few interviews and more from a missing feedback loop. The art of posing the right question is counterintuitive and cognitively taxing, so founders can’t analyze their own

interjectedfuture.com

1

iamwil @interjectedfuture.com · 5d

Doing more customer interviews won't make you better at them. Conversations give you noise disguised as signal: customers lie out of politeness, leading questions get enthusiastic agreement, and you collect expensive fiction thinking it's insight.

1

iamwil @interjectedfuture.com · 5d

What do you use this setup for, other than planning? I’ve also recently started misusing Claude with this Claude Code + Obsidian setup.

1