~/talk

To #comment or not? A data-driven look at...

Talkat DevOpsDays Chicago 2019 · 2019-08-27..08-28· [developer-experience]
github:vzhz
slides:none on file

Data-driven claim: a survey of 170 respondents (scraped/web survey) finds surprising practices and contradictions—60% use inline comments despite norms against them, 63% use comments to explore new ideas, and 78% reject aggressive “no comments” attitudes. The talk reports the scraping and survey method, quantified results, examples of confusing comments, and suggestions about tooling and norms that aim to preserve learners’ scaffolding while reducing noisy, unhelpful commentary.

AI-written summary · about

  1. 0:00Start
  2. 0:42Comments as a learner's first documentation Purpose of comments: → Summaryauthorship, purpose Describe functions
  3. 1:12Best practices we can (usually) get behind Always Docstrings should
  4. 4:27What can we do? → Remember our overwhelmed learner → Advise current them, not future them! → Suggest a deep dive & reading others' code?
~/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.