I have the opposite experience regarding programming questions though. I thought that part of the initial appeal of DDG was that it handled queries that involved syntax or symbols better. I suppose these types of queries may not be that "complex" though. I admit I often query just to verify the API or to check how to do a common task in a language I am less familiar with.

IIRC they won't if you search via !g on ddg.

Some people work better with reference documentation, books and their brain than SO "answers".

Google for "complex programming questions" is laughable and honestly a bit insulting to the profession.

That is also laughable and more than a bit insulting:

- most of the answers (I encountered) are in fact proper and correct answers because bascially it's a peer-reviewed environment, so no need for those snarky quatation marks. I, and many others, have spent hours and hours writing down good answers, and learning quite a bit while doing so.

- DDG/Google/... know about SO so it is often possible to get these answers way faster than when using the reference documentation, and your brain cannot change much about it

- you'll find answers which are nowhere to be found in the reference documentation - I assume your point is that with enough reference documentation and thinking any complex programming problem can be tackled. Well, yeah I guess, but it takes way more time than needed and anecdotally I have seen code written by people thinking that and it was one horrid mess. Mostly because stuff like 'good practices' and insight in design principles and patterns and whatnot isn't found in reference documentation. While via frequenting SO (and similar, before that existed) you pick up this stuff automatically and it makes you reflect on programming which in turn makes you better. If you use your brain, that is.

I find it laughable that you think there is something wrong with looking for resources relating to complex programming questions. I can't tell you how many times Googling a niche and complex problem instantly solved my issue. Sometimes SO is the only site that has fixes for bugs in the program you're using or mistakes in the documentation.