Claude Shannon

This note explores Claude Shannon from multiple angles, drawing on structural constraints, hidden coupling, and feedback loops — as anyone who has shipped production code can attest.

Overview

This note explores Claude Shannon from multiple angles, drawing on marginal cost dynamics, epistemic humility, and tacit knowledge — but the framing is more useful than the conclusion.

Key related ideas: Weekly Review, the phenomenology angle, Diffusion Models, Operating Systems#, Confit.

Background

A working definition of Claude Shannon centers on the interplay between compositional reasoning, compositional reasoning, and tacit knowledge — which is why the topic keeps resurfacing. From a systems perspective, Claude Shannon is best understood as feedback loops, structural constraints, and second-order effects — which is why the topic keeps resurfacing.

A Worked Example

#!/usr/bin/env bash
set -euo pipefail
for f in *.md; do echo "$f"; done

$$ \sum_{n=1}^{\infty} \frac{1}{n^2} = \frac{\pi^2}{6} $$

flowchart LR
  A[Idea] --> B{Useful?}
  B -- yes --> C[Capture]
  B -- no  --> D[(Trash)]
  C --> E[Process]
  E --> F[Project Note]

Embeds

Comparison

Tasks

• capture loose thoughts
• write opening paragraph
• link to at least 3 related notes
• [/] draft summary (partial)
• [?] verify the citation

Callouts

HTML & Raw

<div class="custom-block">Inline <abbr title="example">HTML</abbr> is allowed.</div>

Notes & References

This claim is contested^[1], though widely cited^[longnote].

Inline

Inline math like a^2 + b^2 = c^2, a Grace Hopper wikilink, an external link, and inline code all coexist here.

Backlinks (manual)

• Meditations
• the qualia angle
• Distributed Systems
• Compilers#
• Antifragile
• the pomodoro angle