"Hey, quick question..."
No. Absolutely fucking not.
You didn't have a "quick question." You had a perfectly googleable question that you were too lazy to type into a search bar. Instead, you walked over to someone's desk, or pinged them on Slack, or raised your hand in a meeting, and made your ignorance everyone else's problem. You turned a 10-second search into a 10-minute interruption. You stole someone's flow state so you wouldn't have to read a goddamn search result. Congratulations, you are the reason people wear headphones in the office.
Faster for WHO? For you, sure. You get your answer in 30 seconds without lifting a single neuron. But the person you asked? They were in the middle of something. They had context loaded in their head—the delicate, fragile, hard-won context of whatever problem they were actually solving. And you just smashed through it like a toddler through a sandcastle because you couldn't be bothered to open a new browser tab.
Studies show it takes 23 minutes to regain deep focus after an interruption.
Twenty-three minutes. Your "quick question" about what arguments
git rebase takes just cost someone almost half an hour of
productive work. But hey, you saved yourself 10 seconds. Great trade.
Truly efficient. You should teach a masterclass on productivity.
"But they know the answer off the top of their head!" So does Google. Google also knows it at 3 AM, on weekends, during holidays, and without judging you silently for not knowing something that's literally in the first search result. Google doesn't lose its train of thought when you ask. Google doesn't resent you. Google is a better colleague than you deserve.
Every time you ask someone a question you could have googled, you're not just wasting their time. You're training yourself to be helpless. You're building a habit of dependency. You're telling your brain: "Don't bother learning how to find information. Someone else will do it for you."
And it gets worse. Because when you google something and find the answer, you actually learn it. You read the docs. You see related concepts. You build a mental map. But when someone just hands you the answer? It goes in one ear and out the other. You won't remember it tomorrow. You'll ask the same question again next week. And the week after that. And the week after that.
You know that person on the team who asks the same question every sprint? Who can never remember how to do basic things that everyone else figured out months ago? Who always needs someone to hold their hand through the simplest tasks? That's what you're becoming. That's the path you're on. Every lazy question is another step toward being the person everyone dreads hearing from.
Here's an actual Slack log from a real engineering team. Names changed, stupidity preserved:
Dave asked three questions in ten minutes. Each one is the first result on Google. The first result. Not buried in page five of some obscure forum. The literal first blue link. Sarah was debugging a production incident. She stopped three times to be Dave's personal search engine. Dave thinks Sarah is rude. Dave is the problem.
Don't be Dave.
Fast forward five years. You've been asking "quick questions" your entire career. You've never built the muscle of figuring things out yourself. You've never learned how to read documentation. You've never developed the instinct of "I bet I can find this" that separates competent engineers from dead weight.
Now you're a "senior" engineer. You have the title. You have the salary. But you don't have the skills. You can't debug without someone walking you through it. You can't evaluate a new library without asking the team which one to use. You can't read an error message and figure out what it means because you've spent five years having other people do that for you.
You're not senior. You're a junior with tenure. And everyone knows it. They just stopped correcting you because it's easier to answer your questions than to have the uncomfortable conversation about why you still can't do basic research after half a decade.
The ability to find information independently isn't a nice-to-have. It's the single most important skill in engineering. More important than any language, any framework, any algorithm. Because languages change. Frameworks die. But the need to figure shit out on your own? That's forever.
Before you ask anyone anything, do this:
If you've done all five of those things and you're still stuck? Then ask. Ask with context. Show what you tried. Explain what you expected and what happened instead. That's not a lazy question—that's a good question. Good questions deserve answers. Lazy questions deserve contempt.
"But I don't want to waste time searching when someone could just tell me!" You're not wasting time searching. You're investing in your own competence. You're building a skill that compounds every single day. The 10 minutes you spend finding the answer yourself is worth more than the 10 seconds it takes someone to hand it to you, because next time you won't need to ask at all.
You have a search engine.
You have documentation.
You have a brain that works just fine.
You have everything you need to answer your own question.
You just don't want to.
Just fucking google it.