nexus published, index source

nexus is a threefold documentation resource centered on technology, tools and methods of open research. Threefold means native, external and hybrid documentation. Hybrid documentation is (native) commentary generated when working through (external) resources like guides and tutorials.

The nexus content map

• left-justified links go to published GitHub pages
  • Indented links go to gh-pages source markdown files
  • Each topic is an index.md file and this will have…
    • …one or more children pages, second indentation

Nexus is consequently a 3-level tree.

• nexus published
  • nexus index (L1)
    • lexicon (L1-sub)
    • loose strands (L1-sub)
• bash published
  • bash index (L2)
    • environments (L3)
    • git and GitHub (L3)
    • wrenching the terminal (L3)
    • ssh tunneling (L3, and so on)
• data published
  • data index
    • api
• hpc published
  • hpc index
• cloud published
  • cloud index
    • spot
    • studies
• manim published
  • manim index
• (meta-)documentation published
  • (meta-)documentation index
• python published
  • python index
    • jupyter
    • python packages
• containers published
  • containers index
• artificial intelligence published
  • artificial intelligence index
• quantum computing published
  • quantum computing index
    • Hadamard gates

Essay: Understanding the cloud-for-research time investment

Why is nexus?

nexus was conceived as a response to the tech ‘profusion/latency’ problem: I need to track a bunch of technology with a profusion of details; and I am obliged to spend months focused in one particular area. After long neglect I return to an old topic and find myself re-learning a lot of details. This is onerous and depressing. So to heck with that, nichte diese Töne. nexus documents everything I know to reduce the stress of starting over.