The Developer Guide To Migrate Accross Galaxies.
summary
Six concrete takeaways: software rots — current Word cannot open 1992 docs and Pages once failed on 2005 files — so prefer portable formats and use UTF-8 and write in Markdown. The taxonomy lists six “galaxies” (Babel, Apocalypsia, Paradigmia, etc.), one codebase of 500k LOC takes four hours to build and runs 4,000 tests, and migrations often bloat apps (Swift runtimes, bundled runtimes). Prioritize tests, high coverage, accessibility APIs, avoid proprietary lock‑in, insist on diversity and sane management, and keep eyes on other galaxies.
AI-written summary · about
chapters (8)
- 0:00Introduction and context
- 1:14Defining technology galaxies
- 3:46Babelia and software rot
- 8:46Apocalypsia and legacy code
- 13:49Paradigmia and C++ habits
- 16:31Kulia: East vs West coast
- 20:41Migration and platform drift
- 24:45Guardians of the galaxy
related talks
31mThe Developer Journey
30mTips for Library Development (from a Startup Developer)
29mAging: Evolving Software, Tools, and Ourselves.
58mBusy Developer’s Guide to Polytechnical Engineering
52mKeynote: Steps to Wisdom
11mDo You Want to Take This Code With You into the Future?
46mCode is not important... or is it?
44mRefactoring Ourselves