~/talk

I Just Inherited 50,000 Lines of Code! What Now? — A Practical Guide

Talkat PyData Los Angeles 2018 · 2018-10-17..10-19· [career-development, python]
slides:none on file

Claims concrete tactics for inheriting 50,000 lines: find runnable entry points, run c-loc and tests, expect many tests to fail, treat ~20% of code as “interesting”, and isolate runtime with Docker. Demonstrated dynamic tools: settrace tracing, import hooks with NetworkX, s-trace, object-graph, pdb/gdb and simple histograms to find hotspots. Shows proxies and a toy arwatch VM hook and reports these techniques surface hotspots and runtime dependencies more reliably than pure static reading.

AI-written summary · about

  1. 0:00Inheriting large codebases
  2. 1:57Why 50k lines matters
  3. 9:45Realistic maintenance expectations
  4. 13:36Finding runnable context
  5. 21:45Handling data-driven apps
  6. 27:22Static vs dynamic analysis
  7. 36:54Locating entry points
  8. 44:15Advanced debugging methods
  9. 51:38Preventing future pain
  10. 52:20Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.