The Art of Professional Googling
Description
The image is a screenshot of a Twitter exchange in dark mode. The initial tweet is from David Perell (@david_perell) on July 26, 2020, which reads: 'Becoming world-class at Googling things is one of the most valuable skills you can have, but I don't know anybody who actively tries to get better at it'. Below this is a reply from Mckay Wrigley (@mckaywrigley) that simply says, 'Programmers.'. The humor lies in the profound truth of the one-word reply. For software engineers, particularly experienced ones, 'Googling' is not a casual activity but a core competency that is actively and constantly refined. It's the primary tool for debugging obscure error messages, understanding unfamiliar libraries, researching architectural patterns, and staying current. The joke resonates with senior developers because they understand that effective searching is a skill involving precise query formulation, using advanced search operators, and quickly evaluating the quality of information from sources like Stack Overflow, official documentation, and technical blogs
Comments
7Comment deleted
The difference between a mid and senior dev isn't knowing the answers; it's knowing how to phrase the question to Google so precisely that the top result is a 10-year-old Stack Overflow thread with a one-line answer from a user who hasn't been active since 2013
Senior domain knowledge is just knowing which mix of `site:`, `filetype:patch`, and `-react` turns a 500-line stack trace into the exact Stack Overflow answer you wrote in 2008
After 20 years in tech, I've realized my job title should really be 'Senior Solutions Archaeologist' - I don't write code anymore, I just excavate increasingly obscure Stack Overflow answers from 2011 that somehow still work better than the official documentation
The irony is exquisite: developers spend thousands of hours mastering obscure language features, memorizing Big O complexities, and debating tabs vs spaces - yet the single skill that saves us daily (advanced Google-fu with site:stackoverflow.com, filetype:pdf, and strategic quote placement) remains entirely self-taught through desperate 3 AM debugging sessions. We've collectively achieved unconscious mastery of boolean search operators while consciously refusing to acknowledge it's even a learnable skill. Perhaps the real 10x engineer was the search queries we crafted along the way
Staff-level Googling is turning a 300-line stack trace into a six-word query that lands on a 2018 GitHub issue with a one-line workaround and a closed “won’t fix” PR
Senior devs don't practice Googling; we evolve through survival of the fittest query in the Stack Overflow ecosystem
Our incident runbook is just a list of Google queries sorted by MTTR