Every once in a while, I get questions from random internet folks who want me to do their homework for them. They want me to provide them with detailed technical information, solve their complex design problem, or curate content on a difficult topic so that they don’t have to do the sifting.
While I like to help folks out as much as anyone (and often do), I usually ignore these sorts of questions. Why? Partly, I don’t have enough time to fix the internet. Partly, I like to get paid for consulting. But more importantly, the best technologists first try to solve their own problems.
A Manager’s Perspective
When interviewing candidates for technical positions, one of my questions is, “If you run into a problem you’ve never faced before, how do you solve it?” There are two typical answers.
- “I’ll ask someone else for help. Probably you.”
- “I’ll search the internet, company wiki, and product documentation. I’ll set up a lab. If I’m still stuck, I’ll ask for help.”
I prefer to hire a person who first tries to figure things out. While I want neither a cowboy nor science experiments making their way into production, I do want a motivated individual who will research difficult technical challenges and grow as a result. As that person grows stronger, their team grows stronger as well.
It’s About The Team
Remember that while managers manage individuals, they also manage teams. Hiring decisions are based partly on how well a candidate will fit in with the established team. I view unmotivated technologists as a red flag for team dynamics.
You might feel that if you worked for me, you’d never be allowed to ask a question. That’s not the case. There’s no shame in asking for help at the appropriate time. Technology is hard, and the problems one faces change over time–domain-specific knowledge ages out.
Sometimes a situation is urgent, and you won’t have time to figure out for yourself why { the network is down | the server is offline | the CEO can’t login to the VPN }. All technologists need help to solve problems at certain times. Never asking for help can be just as bad as constantly nagging teammates. However, there’s a big difference between immediately leaning on others and being self-sufficient whenever possible.
When you ask another for help without first trying to aid yourself, you have added to that other person’s workload. You’re cutting into the time they have to get their own work done. Instead of contributing to the team, you’re a drag on team performance. When you make no effort to find your own answers, you weaken your team.
But It’s Also About Yourself
You want to be self-sufficient when you can. You’ll both learn & understand more. Self-sufficiency leads to technology mastery. Technology mastery leads to career opportunities. Career opportunities can transform your life.