What will be the next google? The next Stackoverflow? I doubt it will literally just be a better version of either. It will probably be better IDEs and debuggers. Heck, I doubt we'll continue to type as much as we do...
What will be the next google? The next Stackoverflow? I doubt it will literally just be a better version of either. It will probably be better IDEs and debuggers. Heck, I doubt we'll continue to type as much as we do...
usually when i have to resort to finding someone else's solution i find nothing. its probably a 70/30 or 80/20 split. when it comes to low level or actually challenging problems stackoverflow is more noise than answers. its become a bit like expertsexchange used to be, unless you are a web dev.
Imagine if package management happened this way: say you want to update your version of, oh I don't know, wget. First you Google "wget" and your operating system (analogy for your programming language). Then you open... not the wget page. There is none. You open stack overflow tabs. Not just one either. You look through them, i.e. the answers, the comments about the answers. Finally you find one that people report actually works, you copy a massive block of code into a text file. You make some changes, as it isn't really complete. You save it. You compile it. And, if it worked, there's the latest version of wget, and you move on.
Sound reasonable? Apparently it is for programming languages.
For me and most of the people I know who look things up it's more like, "I am working on this piece of code which is giving an error, and I have stared at it for a bit and I don't see what is wrong. I wonder if others have seen this problem before. I need a bit of inspiration to get me through it." It's almost like paired programming. It's not so much that I am looking for an answer, I am looking for a toe hold in order to push myself just a little higher on a cliff. Inspiration from others experiences helps me to move along quicker. I got this in the past from BBS's, books, and magazines. But now the internet has made that process quite a bit faster and less expensive. And that seems reasonable to me.
I imagine one further step would be to have some AI that can read snippets of your code that are causing problems and match it to similar snippets from Stackoverflow. Let's say your code is (in python):
myCounter = 0
while myCounter < 10:
doSomething(counter)
The AI could realize that it's exactly the same mistake as this code that someone posted on stackoverflow because it ran infinitely: i,n = 1, 50
while i < n:
doSomethingElse(i)
(of course, I used a very trivial example, but you get the idea).this makes me afraid a little. although given the style of your examples i can imagine you have just not had a problem just because of using simple and permissive, modern languages which are difficult to make mistakes with.
due to the nature of compiler errors 99% of the time i can work it out by looking at the line of code.
1% of the time i need to read it carefully because it involves deeply nested C++ templates, and once i find the offending line i fix it 99% of the time in the same way.
the remaining tiny fraction i learn something new. but find that most of the google results are people who failed to solve the problem instead of anything useful, and just have to work it out for myself. i will waste time reading stackoverflow posts with no answers, or answers from people who only want to answer, rather than know an answer. occasionally an apple fanboy will rile me by claiming in some comment that everyone is doing it the wrong way and suggesting something so dumb my head nearly explodes. :)