果然只有5天，如果是中国程序员的话一定会有7天
Everything I googled in a week as a professional software engineer
311–320 of 399 posts
Re: Everything I googled in a week as a professional software engineer
#312Earlier quoted context omitted.
I'm of the opinion that not googling stuff means you're not a proper engineer. And from what I've seen, those who don't google consistently also fail to understand the answers they find when they do google things. It is, in fact, an essential skill.
I’ve asked pre-internet programmers and they said they used to keep reference books at their desk or even a small library/book room at their employers. I’ve heard some government contractors can’t google because they work on non-internet connected computers. They probably keep a lot of books.
I haven't looked anything up in a book on programming in a long time, but I'm not really a software engineer presently. While I rely on Google in general and stack overflow in particular, I don't believe everything is on the Internet. I went through a period where I started to think everything was, but in recent years I realized it isn't.
And just making the decision to type things into Google is far from the ability to search effectively. Increasingly search engines will converge on a bad answer for a given question because it's the most popular. You just cannot assume that the correct solution is going to be prominent, because once another one has critical mass, it cannot be dethroned. The result that sounds just barely plausible enough to fool the average person making the search (not the average programmer) wins, and often it's terribly wrong.
Re: Everything I googled in a week as a professional software engineer
#313果然只有5天，然而如果是中国程序员的话一定会有7天
Re: Everything I googled in a week as a professional software engineer
#314Earlier quoted context omitted.
> Of course that doesn't mean you shouldn't know how advanced data structures work and be able to work with them.. We don't disagree. Understanding data structures is about reaching for the right tool, and very often the hammer of an array/map is the right tool. But the problem I gave isn't that exotic. It's a case where "reaching for an array" is a brute force solution that won't scale. So how do you separate candid…
I would start by asking the question without mentioning scaling at all, and see how they respond. If they immediately jump to using a fancy data structure like a suffix array, but they don't ask any questions about how critical performance and scaling are, then it shows they know a lot of stuff about CS, but they may be lacking in more practical experience. If they tell you they would just use an array or a map (whic…
I totally agree with asking the basic question and then adding scale and complexity.
I don't know if I agree that using a trie at the outset reflects poorly on a candidate. They might see where you are going with the question, even though "you didn't mention scale." Good candidates are going to think about scale at least a little bit. That's not necessarily "lacking practical experience." It's not like basic tries or linked lists are super complex "fancy" data structures.
I think the key is for both parties to communicate thought process. If you're concerned about overengineering then prompt them to explain why they didn't choose an array.
Re: Everything I googled in a week as a professional software engineer
#315Earlier quoted context omitted.
I’ve tried Bing. Many of the result were unrelated to my question.
Google does such a good job with personalized results, that we have have forgotten how to search. Remember the old days when using a search engine effectively was a specialized skill? Search engines have gotten a lot better since then, but a lot of the improvements have been due to personalized results. It’s not easy to transition from Google to Bing or DuckDuckGo. That being said, Google is also a good search engine…
Using a search engine is a more specialized skill than ever.
What "Google getting better" actually means is that it is more likely to return what most people want as the first page hits. That is a tradeoff, because it obscures everything else whenever what most people want is wrong.
As a programmer, you're only going to be doing searches for things that are non-obvious, so there is a vastly higher chance of Google giving you the wrong answer than for the average search.
There is a fundamental contradiction between a search engine that tries to show you only what it thinks you want, and the fact that you don't know exactly what you want when you search, until you see some results.
I think there's something like a conservation law, that the more you make it easy to find some things on the Internet, the harder you make it to find others. Kind of like the proof that you can't compress all strings.
Re: Everything I googled in a week as a professional software engineer
#316Earlier quoted context omitted.
Ok.. Find all the words that match a search string prefix. I.e. you have a search field and want to show the possible matches as you type. With each new char you’re calling this search and getting back a list of words. The dictionary is in memory in whatever data structure you choose. You only have to return matches if the search is 3 or more chars long. Now, how does your implementation scale when the dictionary has…
Load it all into Elasticsearch and just do an API call.
Network latency is an issue then. The word list is going to lag behind keystrokes. Also, doesn't work offline.
Re: Everything I googled in a week as a professional software engineer
#317Earlier quoted context omitted.
> I don’t know a single developer that thinks “googling stuff means you’re not a proper engineer.” Yes the whole interview process is based on the idea of doing stuff for the company that you wouldn't actually do. Indeed I interview my candidate's ability to find resources, to know what considerations are needed, how to deal with IDEs, collaborative tools, the git protocol. I will fire someone on the spot for impleme…
Are you hiring?
No, but I hope other organizations can adopt my approach.
Re: Everything I googled in a week as a professional software engineer
#318The art of googling.. I'm a nobody. I don't write codes I'm no engineer. Im just a regular person. I love google. Only thing i don't understand in their maps how definite is the location of the raw data. Is it100%?
Re: Everything I googled in a week as a professional software engineer
#319Also Google anki method.
Re: Everything I googled in a week as a professional software engineer
#320This is probably a 10-50x fewer searches than I do in a week. I am assuming there are many searches left out. I'd be interested in seeing how the OP tweaks their searches as the results don't return exactly what they want. Here is an actual single search progression for me (In reverse order because copy/pasta :shrug: react context optimize rerender "props.children" react context optimize rerender react usereducer dis…
could you give an example of a complex search? I've never bothered using advanced Google search patterns
Verbatim word match:
“word”
Verbatim phrase match:
“some phrase”
Verbatim word negation:
-“word”
Verbatim phrase negation:
-“some phrase”