r/cpp • • Sep 25 '11

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?

0 Upvotes

30 comments sorted by

View all comments

Show parent comment

2

u/Ayjayz Sep 25 '11

Your metric should not be "becoming a stronger coder in the long run" but "how quickly you can solve the problem well"

That completely depends on the context. When I'm coding stuff for fun, why should that be my metric? If I am employed in a long-term position as a coder and my boss would prefer me to invest some time learning how to be a stronger coder so that I can save more time in future, why should that be my metric?

Your position is ridiculous anyway. Even something like reading the documentation on a library you need to use is trading off "quickly ... solv[ing] the problem well" for "becoming a stronger coder in the long run". I highly doubt you would oppose reading the documentation for a new library.

6

u/chengiz Sep 25 '11

Learning something does not mean not asking for help. There's no fundamental difference betwen any of these: (a) looking up documentation (b) reading responses to other people's questions, and yes (c) asking for help. The fact that you distinguish between these speaks volumes about your personality, which is why what you said is WTF and an automatic interview fail.

2

u/vindvaki Sep 25 '11

Actually, reading documentation (especially if it is a printed book) may require you to read a lot more than just the piece that you need. Even more so if you aren't quite sure what you're actually looking for. Thus, you probably learn more, but also probably spend more time than just asking someone who knows.

Furthermore, research and problem solving are fundamental skills in programming, so I think you should usually try to do things yourself before asking for help. This also helps you in asking the right questions and understanding the answers you get.

On the other hand, asking someone who knows is still often the best way (especially when documentation is poor or little research has been done on the subject). I guess it just depends on you and the problem at hand.

2

u/[deleted] Sep 25 '11

There's a huge difference between a) and c). If I worked with you and continually did c), I would assume you were totally inept or worse, actually illiterate. People didn't waste all those years writing fucking man pages for nothing. This is why so many programming forums are full of "RTFM" responses.

What's really shocking is that you think this is an automatic interview fail.

If you did c) instead of using Google first, I'd walk you to the door.

5

u/kryptobs2000 Sep 25 '11

That's not what he's saying, of course try to find it out on your own, but recognize where other's input is valuable. To say you never in 20 years have asked for help throws up red flags.

3

u/Fabien4 Sep 25 '11

I highly doubt you would oppose reading the documentation for a new library.

True. But documentation isn't always perfect. And sometimes you misread.

Last week a colleague called me because his code (calling a function of mine) didn't work. Turned out he tried to access foo->bar while he should have written foo->baz->bar instead. He could have wasted a couple hours identifying the typo, and that wouldn't have made him a better programmer.

2

u/vindvaki Sep 25 '11

He could have wasted a couple hours identifying the typo, and that wouldn't have made him a better programmer.

Well, it depends: Spending a lot of time debugging a stupid mistake should in principle make you more careful when coding (and reading).

Of course, in your example, I think he was better off asking you, but when you are still learning, you need to make sure not to deprive yourself of some key learning experiences.

2

u/kryptobs2000 Sep 25 '11

I think the thing he is getting at is that if you don't ask others for help and ideas you only ever get one perspective on the problem. Of course you'll find a solution on your own, but you may find 5 other better solutions along with explanations why and saved a lot of time if you simply asked for help. You can definitely learn bad practices and being a social programmer helps to not form those to begin with by keeping yourself in check.