Topic: code written

7 chunks · 6 episodes

Topic summary

?
A short read on the topic's time range, peak episode, and strongest associations. Use it as the quick orientation before drilling into examples.
  • code written appears in 7 chunks across 6 episodes, from 2024-02-12 to 2026-01-19.
  • Its densest episode is Bits and Bobs 8/19/24 (2024-08-19), with 2 observations on this topic.
  • Semantically it travels with llms, vast majority, and black box, while by chunk count it sits between code execution and emergent force; its yearly rank moved from #110 in 2024 to #167 in 2026.

Over time

?
Raw mentions over time. Use this to see absolute attention, not relative rank among all topics.
Mean 1.2 mentions per episode across the full range2024-02-12: 1 mention2024-07-01: 1 mention2024-08-19: 2 mentions2024-09-09: 1 mention2025-04-21: 1 mention2026-01-19: 1 mention2024-02-12: 12024-07-01: 12024-08-19: 22024-09-09: 12025-04-21: 12026-01-19: 12024-02-122024-09-092026-01-19

Observations

?
The primary evidence view for this topic. Sort it chronologically when you want concrete examples behind the larger pattern.

Things written by LLMs are slop.

from Bits and Bobs 9/9/24 ·

Things written by LLMs are slop. Integration code written to combine disparate things is glue code. Glue code written by LLMs is glop. Glop is a kind of black box; it doesn't need to be understood necessaril...

The same origin model is too coarse.

from Bits and Bobs 8/19/24 ·

...ion over time. But if the value of software is the combinatorial possibility of code written by different people being composed into new wholes, then across-origin should be common. A system that leaned into making across-origin compositions ...