111–120 of 181 posts
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.
Related is being good at debugging. There's something about having a certain intuition (in reality probably experience) on what it is that you are looking for that is critical.
Earlier quoted context omitted.
Related is being good at debugging. There's something about having a certain intuition (in reality probably experience) on what it is that you are looking for that is critical.
Like when you are looking at live debugging information that is scrolling fast but you are still able to pick out problems?
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…
However, even more often I find answers that I upvoted in the past (sometimes I deliberately look for them, sometimes by accident). When I see an upvote from myself, I can be sure I can immediately use the answer because I already verified it in the past. SO is like a big, googleable, writable public wiki for me, with annotations.
It amazes me that many colleagues do not have an account, or have an account but never write or upvote anything.
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…
Happened to me several times to find my own answer/question on SE, or one of my work colleague's. However, even more often I find answers that I upvoted in the past (sometimes I deliberately look for them, sometimes by accident). When I see an upvote from myself, I can be sure I can immediately use the answer because I already verified it in the past. SO is like a big, googleable, writable public wiki for me, with an…
The free rider problem is real, that's for sure.
I'm in 100% agreement.
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…
If I find a problem I can't solve I will post a question on Stack Overflow, then I go back to work trying to solve it. If I find the solution before someone else does I answer my own question on Stack Overflow.
My most updated answers have been to questions I asked in the first place.
I also get a chuckle when someone I know says they were googling a problem and found my post on Stack Overflow.
Earlier quoted context omitted.
Yet we force people in interviews to remember things standing in front of a whiteboard.
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…
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 point to close to 200 public sites I've built (both dynamic and static) and have a portfolio full of images from other projects I've worked on.
If you can't ascertain whether a person has practical experience with a tool, software, or language then you're not doing your due diligence.
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…
I'd say at least half of the questions/answers I come across are closed flagged as vague, or whatever but at the same time, were incredibly informative, useful and exactly what I was looking for.
The SO moderators need to chillax a bit.
Earlier quoted context omitted.
Do it in a VM, and it is.
A VM is also just software, plenty of quest-to-host escapes in the last few years... I bet that many people that should know better here have never updated their VM, except those who are warned by the auto updater that is.
Not to say that this is not actually a security threat, but I would say a VM is safe enough