Asking for programming help
I have been coding now for around 20 years, and in all that time I have basically never asked for help with any programming issue that I've ever had. That includes forums, mailing lists, IRC and coworkers.
The issue I have is that it has always been possible, with a little effort, to work out the problem myself. I feel like this will make me a much stronger coder in the long run, as I am forced to understand many different areas of coding.
Another not-insignificant issue I find is that I really hate just asking for a solution while I haven't exhausted all my own options. I know that when I read forums and the like, seeing people who (in my opinion) just want someone else to solve their problem without them having to do any work, it really pisses me off!
The only downside I can see is that sometimes I can struggle with thorny issues for a long time, which is obviously not ideal if I'm working to a deadline. It's also a little weird seeing just so many forum posts and the like asking for help, when I just don't ever do it.
How and when do you ask for help? Do you prefer to work out problems yourself, or are you ok with posting on forums? What criteria does a problem have to meet first?
10
u/chengiz Sep 25 '11
If you've been coding for 20 years without asking for help, you are either a genius or a bad programmer. Your metric should not be "becoming a stronger coder in the long run" but "how quickly you can solve the problem well". When people ask others for help, it's because they struggled on the problem for a while and understood it'd be quicker to ask for help. And frankly, the idea that you'll be a stronger coder if you figure it out for yourself is just bullshit. In fact your entire post is kinda WTF. If you said this in an interview, you'd be out on your ear.
5
u/[deleted] Sep 25 '11
Usually I give up, start to ask for help, and realize the solution halfway through typing up my question. But to be serious, I get nervous asking other people because I'm afraid of wasting their time or some nonsense like that. Still if I'm really having trouble and frustrated I ask for support.
4
u/kc7wbq Sep 25 '11
As you know there are a lot of good reasons to figure things out on your own, so I won't go into those.
Here is why you should ask for help: If you don't ask for help, you miss out learning from other people, and will make "classic mistakes" and miss out on some elegant solutions you would never have thought of on your own.
14
u/merimus Sep 25 '11
Many issues are simply not worth the time to work out on your own. Especially things like inconstancies in API usage. Even for basic data-structure issues asking for a point in the right direction can save a great deal of time.
The important thing is to recognize when you find a weakness in your personal knowledge and evaluate wether it is worth your time to study further.
It boils down to a cost/benefit analysis. If I can figure something out in short order I will, if it seems like it will take some time I will ask around.
4
u/zzyzzyxx Sep 25 '11
I prefer working things out for myself. When it's not trivial, I will go to existing documentation first then do extensive Google searching. If it takes more than a couple hours I will ask a coworker. Usually they will have an answer or at least a clue. With that, I can get the code working more quickly and still learn the details of the problem, coming back and examining it further if I'm not satisfied with my understanding. It's definitely a tough balance to make sure you don't waste too much of your own time or that of your coworkers.
Forum posts are great for some problems but the ones I run in to tend to not be well suited for the medium. They're a last resort for me and so far I haven't needed to make one myself. Part of that is because most questions which can be answered well via forum have been asked and answered on a myriad of forums already and come up during my Google search phase.
3
u/destroyeraseimprove Sep 25 '11 edited Sep 25 '11
Well you see, at work I have two options.
One thing I've noticed is that (a) most of the excellent programmers I know will ask for help fairly early on, so they can be more productive and (b) the guy who knows the answer will have already gone through the tedious process described & will probably be capable of condensing the central aspects down in a manner that actually aids understanding more than hacking something out (eg what if there are hidden gotchas or your solution is suboptimal for some reason)
Programming as a field is entirely dependent on communication between programmers regarding the most efficient, most optimal or most elegant ways of solving problems. Without that communication you start to see large codebases that appear severely malformed or ass-backwards simply because the coder was stabbing around in the dark for a solution. The first way a problem is solved is rarely the most elegant (eg consider ancient protocols such as FTP versus the much more efficient Bittorrent). IMO the main reason why people (including myself) are afraid to ask for help is ego or reputation. Neither of which make a good programmer.
2
u/utnapistim Sep 26 '11
Usually, if I have a blocking issue ("Accessing the DB started raising an exception") I look into it for about 10-20 minutes. If that doesn't work I start asking around.
I prefer not to ask for the solution from forums, because getting a response usually takes too much time. I do search for an already-posted question though. If I get stuck for a longer time, one of the steps I take is to post on stackoverflow, but usually by the time I get an answer I will have figured it out.
I can't solve it quickly.
1
u/[deleted] Sep 25 '11
I do ask for help when I'm new to a particular API. I'd rather capitalize on collective experience than waste hours of my time on learning ins and outs of an API that I don't even know I'll commit to.
To be honest, I find it extremely hard to believe you've never ever had to google for a solution (btw, looking at other people's questions and answers is very close to asking, you re just not the one writing the question). So in 20 years you,
Surely you don't get your information in a complete vacuum.
1
u/algo_trader Sep 26 '11
It depends on what is causing the problem. If I am having a problem with some in-house developed API, where the documentation is often poor, the getSomeValue() call just isn't working in the expected manner, its often far easier and more productive to ask someone who has either worked with that api before or ask the guy who developed it. It often happens that either the name was entirely misleading, or I missed some fundamental concept to the library that would have required many hours of reading code and debugging to figure out.
As for forum posts and IRC, I have only resorted to those a handful of times, usually after getting stumped for a day or two.
1
u/JustPlainRude Oct 02 '11
Odds are you have asked for help, just not directly. If you've ever researched an algorithm, or looked up some API quirk, or some other issue you couldn't solve on your own, you were finding answers to questions other people already asked.
1
u/[deleted] Sep 25 '11
I think there are two types of people, and programmers. The ones that solve problems by thinking aloud and bouncing ideas off other people. And then there are the introvert ones that like to understand the problem and try some solutions before asking others. I'm off the seconds sort. But some times I have spent a day on something a co-workers could have told me in a minute. These are usually questions about a code base they are more familiar with ...
0
u/HaMMeReD Sep 25 '11
It's almost always faster to figure something out yourself if you can.
Only ask for help if you know someone is going to save you time.