Lessons from a Librarian
summary
A concrete playbook for removing long‑lived tech debt: separate API and implementation modules to avoid rebuilds, use IntelliJ structural replace and custom plugins plus terminal tools like find/xargs/z or Python/Kotlin scripting to rewrite code, run android lint and error‑prone checks, incubate changes with shadow jobs, and migrate at scale — the team moves thousands of files in days with no regressions while keeping stacktrace tracking and celebratory tombstone cakes.
AI-written summary · about
chapters (12)
- 0:00Start
- 3:36Lessons from a Librarian
- 5:54API Design
- 6:26Limit Surface Area
- 9:20How easy is it to do the wrong thing?
- 9:36API vs Implementation
- 13:03Code Review
- 13:28Static Analysis
- 14:33Removing Tech Debt
- 18:32De-risking Change
- 19:24Shadow Jobs
- 20:31Offensive Programming
related talks
54mAvoiding a Shared Library Nightmare
23mDevOps and Legacy Code
47mTales from the Dev Side: What Went Wrong, What We Fixe & What You Can Steal
18mTackling tech debt
42mLessons from Modernizing the Tech Stack of a Top App
52mFrom Laptop Builds to Advanced CI
01h 02mTools for simplified large scale systems
43mLibrary Developer Confidential