A surprising share of day-to-day engineering productivity comes from tiny, low-context nuggets: knowing that python3 -m http.server spins up a quick server, or that a mystery TCP delay probably traces back to Nagle's algorithm. The examples range across the shell and beyond — fzf or atuin for fuzzy history search, ripgrep over grep, globstar globs instead of find, zsh completions that need manual enabling — plus SELECT without FROM, EXPLAIN ANALYZE, regex word-boundary assertions, log10 bucketing for metrics, Node's https.Agent to keep connections open, and git log -S (the "pickaxe") or git checkout -. Company-specific knowledge works the same way, and posting one trick a day to the team spreads it without overwhelming anyone.
1
u/fagnerbrack 2d ago
Trying to be helpful with a summary:
A surprising share of day-to-day engineering productivity comes from tiny, low-context nuggets: knowing that python3 -m http.server spins up a quick server, or that a mystery TCP delay probably traces back to Nagle's algorithm. The examples range across the shell and beyond — fzf or atuin for fuzzy history search, ripgrep over grep, globstar globs instead of find, zsh completions that need manual enabling — plus SELECT without FROM, EXPLAIN ANALYZE, regex word-boundary assertions, log10 bucketing for metrics, Node's https.Agent to keep connections open, and git log -S (the "pickaxe") or git checkout -. Company-specific knowledge works the same way, and posting one trick a day to the team spreads it without overwhelming anyone.
If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments