Small programming tricks(will-keleher.com)
645 points by signa11 27 days ago | 278 comments
tl;dr: Engineering productivity often comes from accumulating small, high-leverage tricks that don't require deep expertise—like using `fzf` for fuzzy shell history search, `git log -S` to find commits that added/removed a string, `explain analyze` in Postgres/MySQL, or replacing `find` with shell globstar patterns. Company-specific nuggets (who to ask, which data source debugs what, how to trigger a rolling restart) are equally valuable. The author suggests senior engineers share one trick per day with their team as a low-overhead way to spread knowledge.
HN Discussion:
  • ↑Sharing personal favorite shell/programming tricks that reinforce the article's premise
  • ~Knowing tricks isn't enough; building habits and discoverability tools are the real challenge
  • ↑Watching AI work is a modern way to discover new command-line tricks
  • ~The article mislabels these as programming tricks; they're really CLI/computing tricks with broader implications
  • ↓Daily trick-sharing in team chat would be annoying rather than helpful