121–130 of 181 posts
I not only use Google frequently, I use it to search for things I myself have written in the past. I can't count the number of times I've Googled for a programming question where the answer is found on a Stack Overflow page I've written. If it's a particularly old answer that I've completely forgotten, I've even thought to myself, " Wow this genius sounds just like me! "[1]. [1]: ... as well as " This idiot has no cl…
2. Hope you're using OSS software and simply browse the source to find answers.
The second approach is a bit slower at first, but after you dismantled a bunch of repos it becomes natural, you get faster and the answers you find are more reliable.
Earlier quoted context omitted.
Or a question you had years ago. Couldn't find an answer. So you did a workaround and/or forgot about it. Now you hit the same problem search -- and find you original question. But wait! Now there are half-a-dozen other people with the same problem! So you click on all of those links. But none of them could find an answer either. Bonus points if there's a guy who comes in condescendingly and quotes a manual or some o…
I had a guy, on stackoverflow, commenting condescendingly on my question (or was it an answer, can't remember) that I was wrong and I should edit my post with his answer instead. All would be well if it wasn't on a 6 year old post at the time, and he was wrong. Ah, stackoverflow - what happened to you? It was fine and dandy when it was all loose. Now you ask a question and it's immediately flagged for various reasons…
It took two hours to carefully craft my question just to have it immediately shot down. It is needless to say I have not posted again since.
Earlier quoted context omitted.
That and finding a question you've search for, only to find out that question was also posted by you years ago. Bonus for ones with no answers still.
Extra bonus, if closed as "not a real question", heavily upvoted, at the top of the Google's 1st page of search results, and actually containing a (heavily upvoted as well) solution. P.S. Recursive bonus: closed with a comment ("you should just google it") and now actually the top result in search output (happens quite frequently) :)
To comment on the headline, I am an experienced developer who also uses Google and DuckDuckGo several times per day. It's often faster to look up a method in the Java or Ruby stdlib that way, rather than navigating through the official docs hierarchy.
Earlier quoted context omitted.
How much you remember is also correlated to how much you actually use certain things; it can be a good signal for whether you have practical experience with X. For some companies, it's what they need in a hire. For others it's OK to just ensure people have a sound problem solving strategy and above-average general cognition. I think you'll find varying levels of what you might consider nitpicking depending on the sor…
>> it can be a good signal for whether you have practical experience with X. This should be vetted out well in advance of an interview, especially for a developer. If you don't have at least a half dozen repos somewhere with code examples of sites or apps you've built, then there's a very high chance you're not going to get an interview. I've only been coding for 7-8 years and I have an extensive GitHub page, can poi…
I not only use Google frequently, I use it to search for things I myself have written in the past. I can't count the number of times I've Googled for a programming question where the answer is found on a Stack Overflow page I've written. If it's a particularly old answer that I've completely forgotten, I've even thought to myself, " Wow this genius sounds just like me! "[1]. [1]: ... as well as " This idiot has no cl…
For example: https://data.stackexchange.com/stackoverflow/query/edit/4811... sum and average of posts score who have a comment starting with the word hacker or news.
That doesn't mean you just copy and paste whatever you find. But it means you are now more informed than you were before and can come to a better, faster solution.
I don't know if I am experienced or not (beyond the numbers of years programming) but I am sure "search engine oriented programming" give you a lot of advantages and connect dots that take years if you follow other routes.
I often joke that my ability to formulate good Google queries is the single most important part of my software engineering skillset. Except, you know, I'm not really joking.
Don't undercount that you also have the skill to determine whether an answer on stackoverflow (etc.) is actually correct and worthwhile. (I taught intro to CS for the first time last year, and watched people get very hung up by subtly broken things they found on the innertubes. To the point where we simply told them not to - we'd much rather have them asking the course staff, until they've developed the experience to…
I eventually got things working, though I feel far from confident about openGL ES. Actually, embedded shader code, packed arrays, limited debugging and my rusty matrix algebra doesn't make it easy.
Let's say tomorrow there was some major catastrophy in which every disk drive or tape drive was wiped, and every computer had reset. How would we fare in rebuilding society? I guess it would be similar if in 1950, all of books lost their ink or all of scientists/engineers had amnesia. I'm not trying to make a point other than it is interesting to think about it.
Humanity would have to come together to reconstruct Angular and Bootstrap from the ground up.