The pursuit of a perfect map didn’t merely fail, it killed the discipline of map making.

On Exactitude in Science Jorge Luis Borges, Collected Fictions, translated by Andrew Hurley. … "In that Empire, the Art of Cartography attained such Perfection that the map of a single Province occupied the entirety of a City, and the map of the Empire, the entirety of a Province. In time, those Unconscionable Maps no longer satisfied, and the Cartographers Guilds struck a Map of the Empire whose size was that of the Empire, and which coincided point for point with it. The following Generations, who were not so fond of the Study of Cartography as their Forebears had been, saw that that vast Map was Useless, and not without some Pitilessness was it, that they delivered it up to the Inclemencies of Sun and Winters. In the Deserts of the West, still today, there are Tattered Ruins of that Map, inhabited by Animals and Beggars; in all the Land there is no other Relic of the Disciplines of Geography. " - Suarez Miranda,Viajes devarones prudentes, Libro IV,Cap. XLV, Lerida, 1658

"In the elder days of Art, Builders wrought with greatest care Each minute and unseen part; For the Gods see everywhere." - Longfellow

Terrain Disclosure is when a map implies something before you’ve asked it anything. Search answers the questions you already know to ask. You type, it retrieves, and whatever you didn’t think of stays invisible. A semantic terrain works the other way around. Lay out a whole corpus by meaning, and the shape starts implying things on its own. Two topics you assumed were separate turn out to share a ridge. Or there’s a valley where you’d have bet on a mountain. You didn’t query for any of that. The terrain disclosed it, because it was there, and the previously unasked questions come next

Tech debt is forgetting why something was built the way it was. Release drift is forgetting what’s actually running versus what you think is running. Security holes are mostly forgetting that a path exists at all.

brownfield remediation

Agentic coding encounters diminishing returns as an application matures. Generating changes remains fast, but integrating them into a coherent, dependable product becomes increasingly demanding. Each change must preserve more existing behavior, fit established architectural and visual decisions, and pass through build and testing cycles that delay feedback. A seemingly small update can affect navigation, saved state, background processes, and the balance of an interface. Its implementation may take minutes; establishing that it works properly across the application can take much longer. Quality updates require actual end-to-end testing and careful attention to the application’s order, clarity, and beauty. As a product matures, agentic efficiency depends increasingly on keeping changes well scoped, preserving understanding, and verifying the complete experience.

Créneaux

A feature with no path to it is unreachable, built and invisible. A path that leads to no feature is vaporware. Product-market fit is when the distance shrinks to nothing.

is there a such thing as fingerprint similarity vectors?

Rogers’ diffusion of innovations : Relative advantage: is it clearly better? Compatibility: does it fit how people already work? Complexity: can they get it quickly? Trialability: can they try it free? Observability: can others see them using it?

A map carries the authority of neutrality.

If software development only started and ended at "adding features" , then we would all be engineers.

Claude seems to take more personal ownership of a project, or task. Maybe a kind of care.