Skip to content

Latest commit

 

History

42 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Same Difference

I spend a lot of my time deep in podcasts, interviews and articles — some from construction, plenty from completely different fields. Now and then two of them click: a point from one lines up with a problem I keep running into somewhere else. These notes are those moments — when two things that seem unrelated turn out to be surprisingly connected.

Structure

  • Each note is a standalone Markdown file in the repo root.
  • Notes use YAML frontmatter with groups:, tags:, and date:.
  • Related notes are linked with wiki-links in the body/footer.
  • External citations live under Sources: as raw URLs in the footer.
  • The GitHub Pages reader lives in docs/ and is generated from the Markdown vault.
  • The archive is date-first, grouped by year, and opens the latest note by default.
  • Clicking a tag inside a note filters the catalogue immediately.

Working with notes

  • Keep notes prose-first and concise.
  • Add or update date: in frontmatter when creating a note.
  • Use AGENTS.md for the local agent instructions.
  • Use Sources: only for external URLs and keep them as raw links in the markdown footer.

Validation

Run the note linter before publishing changes:

bash ./lint-thoughts.sh

Generate the Pages manifest when notes change:

node ./scripts/build-site.mjs

About

A collection of thoughts on construction, product thinking, AEC, AI, and digital transformation.

Topics

Resources

Code of conduct

Stars

0 stars

Watchers

0 watching

Forks

Contributors

Languages