~/talk

TODO: Should We Stop Leaving TODOs in Code? πŸ€”

TalkinFrenchat Sunny Tech 2026 Β· 2026-07-02..07-03Β· [developer-experience]
name:Ando Nary
github:andonary
slides:none on file

Examines why TODO comments appear in code, distinguishing when they indicate poor quality or intentional notes, and explains why teams write them. Describes strategies and organizational practices to reduce and manage TODOs (from TODO to DONE) and gives concrete examples of TODO usage in code.

AI-written summary Β· about

  1. 0:00TODOs in code
  2. 1:15TODO example in codebase
  3. 4:05Team debate on removal
  4. 5:32Boy scout method rule
  5. 6:34Refactoring with Clean Code
  6. 7:57Focus on bug fixing
  7. 9:00Iterative approach with TODOs
  8. 10:04Self-resolving TODOs
  9. 11:36TODOs as temporary fixes
  10. 12:45TODO ticketing integration
  11. 13:49Comments vs TODOs
  12. 15:14TODOs for maintainers
  13. 15:55Local TODO best practices
  14. 17:46TODO categories summary
  15. 18:52Q&A
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 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
← β†’
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
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.