~/talk

Reading code

Talkat Devoxx UK 2025 · 2025-05-07..05-09· [developer-experience, career-development]
slides:none on file

Research claim: developers spend 58% of their time reading existing code. Concrete practices shown include running printed two‑page snippets through structured exercises like first glance and “pick five important lines” to build empathy and spot domain gaps. Tool demos use IntelliJ IDEA: dependency matrix, endpoint/Swagger navigation, bookmarks, debugger with evaluate expression, refactorings, and AI features to explain code, generate docs/tests, and summarize git commits. Expect practical, reproducible techniques and examples rather than abstract advice.

AI-written summary · about

  1. 0:00Introduction to reading code
  2. 1:47Why reading code matters
  3. 5:43Code reading club exercises
  4. 15:53Understanding a new codebase
  5. 24:49Navigating code with IDE tools
  6. 31:37Structured exercises for complex code
  7. 38:55Tests and debugging for comprehension
  8. 45:12Git archaeology and AI assistance
  9. 47:19Next steps and resources
~/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.