Getting Ahead By Deleting Code
summary
Claim: career impact grows by deleting other people’s code and mentoring, not by counting lines. Concrete practices: use PowerShell, enforce thorough code reviews, run weekly (moving to twice‑weekly) group exercises like LeetCode/Advent of Code, and pair program with VS Live Share. Evidence: support for 400 microservices requires scalable mentorship; helping colleagues delete 50 lines can drive a net-negative lines of code metric. Outcomes include clearer, faster, safer scripts, higher team velocity, and increased hiring visibility.
AI-written summary · about
chapters (10)
- 0:00Intro
- 2:25HOW SOME PEOPLE MEASURE DEVELOPER IMPACT
- 5:30LET'S TALK ABOUT LEARNING TO WRITE CODE
- 10:07REVISITING THE ORIGINAL QUESTION
- 13:33THE BENEFITS OF FLEXIBILITY
- 16:29CODE REVIEWS
- 24:13GROUP LEARNING
- 28:05PEER PROGRAMMING
- 32:36ONE ON ONE MEETINGS
- 38:21DON'T SEEK A BIGGER SLICE OF A SMALL PIE
related talks
01h 01mDoes Your Codebase Spark Joy?
27mThe art of deleting code
01h 22mHow to Delete Code
10mAccessibility of codebases: Leader’s perspective
38mDeleting Code Is Hard And You Should Do It
47mMentoring technical practices, what works and not
35mFive Lines of Codes
54mReadable Code: The Secret to Clean, Productive Software