Everything I googled in a week as a professional software engineer
1–10 of 399 posts
Re: Everything I googled in a week as a professional software engineer
#2Fourth item on Monday: "undo a rebase - oops."
Re: Everything I googled in a week as a professional software engineer
#3This is a really interesting peek into the developers mind. Right away I notice I google things differently than the author. I try and hit up phrases that match a question (which is why I probably over index on stack overflow). The author seems to hit up ideas that remind me of something that might be the title of a blog post or something. Also, my search is definitely more full of stack trace keywords. Probably 80% stack trace keywords by weight.
Re: Everything I googled in a week as a professional software engineer
#4I love that I’m not the only person that thinks about this still
“dl vs ul”
Re: Everything I googled in a week as a professional software engineer
#5I'm actually surprised the list wasn't way longer with much weirder queries.
Re: Everything I googled in a week as a professional software engineer
#6I appreciate this as some newer developers I have worked with have been concerned that Googling things is something they need to grow out of. Google engineers, being somewhat revered in my Big Corp, Googling things every day would go a long way to encourage them.
Re: Everything I googled in a week as a professional software engineer
#7On the list of things I always Google, is how to create a symbolic link under Linux. I just can't figure out a way to remember what comes first; the source or the destination. The man pages add to the confusion by calling the "source" the target. So, the rule of thumb I now follow is cp or mv semantics.
Re: Everything I googled in a week as a professional software engineer
#8This is a really interesting peek into the developers mind. Right away I notice I google things differently than the author. I try and hit up phrases that match a question (which is why I probably over index on stack overflow). The author seems to hit up ideas that remind me of something that might be the title of a blog post or something. Also, my search is definitely more full of stack trace keywords. Probably 80%…
I almost never search for stack traces: I pick out class names or error codes and search for that instead. How's your success rate with finding useful information?
Re: Everything I googled in a week as a professional software engineer
#9I love that I’m not the only person that thinks about this still “dl vs ul”
ul = countable items in arbitrary order
ol = countable items in a pertinent sequence
dl = key value pairs
table = a matrix of three or more keys and values
Re: Everything I googled in a week as a professional software engineer
#10"Never memorize something that you can look up." -Albert Einstein
edit- Had to look up who actually said this