[halfastack]

I looked over the Linux questions, and they were pretty bad:

Q.1: What is the core of Linux Operating System? Shell

Kernel

Command

Script

Terminal

I mean... If they asked me about that at an interview, that'd be a huge red flag. I wouldn't consider this list when studying for interviews... It is sad for me how many stars and forks this list has. Hopefully, it's much better for other languages/topics.

[kraftman]

Is it supposed to be a list of good questions you should ask, or crap questions you should prepare to get asked?

[jcranmer]

The repository name is "awesome-interview-questions". So far, of the 3 lists I've looked at, [1] was a page where someone apparently deleted random swathes of text in the middle of the content and utterly unusable as a result, and [2] and [3] were both full of grammatically poor questions that ask about minutiae of C++, get it wrong, and don't realize that C++11 exists.

I think it's supposed to be a list of good questions to ask, but it's actually a compilation of lists that people sent the author with very little to no curation actually done.

[1] http://placement.freshersworld.com/power-preparation/technic...

[2] https://pangara.com/blog/cplusplus-interview-questions

[3] http://a4academics.com/interview-questions/57-c-plus-plus/41...

Edit: Just opened up a Java list for #4... and it said that LinkedList was usually better performance over ArrayList. That is not correct; ArrayList is usually better (because of cache locality). So I'm now 4 for 4 on bad lists out of this site.

[technion]

This really seems to be the trend with "Awesome" lists. It's not often they appear to have much curation at all, it's frustrating to see them end up with thousands of stars. Often an order of magnitude more than many open source projects.

I quite enjoyed the Erlang questions. Apparently "what is Erlang" is a common Erlang interview question.

[rwnspace]

Generally speaking, I consider them a noobtrap for two reasons.

First off, many of the resources are written and submitted by people who have no place teaching others - and are writing almost purely to self-promote and have something to show to employers.

Second, even if some of the resources in there are of decently high quality, the probable best schema for how to use and integrate that resource is going to be bound up in a textbook written by Someone Very Important. Along with all the stuff you really need to know anyway.

Scrap that, three reasons. Finding and aggregating these kind of links for your personal use is of value: it develops your taste and sense of what resources to veto, and what to collect, and is a meta-skill applicable everywhere you have a search engine and some curiosity.

In '17 and early '18 I wasted hundreds and hundreds of hours collecting "the perfect" set of bookmarks for various things I want to learn, and my collection method has basically been to scrape these kinds of lists and apply a surface-level "ooh sounds cool" filter to what I pick up. Obviously, I learned very little doing this, and almost never open such links except as part of a half-hour flight of fancy.

Perhaps if you're of intermediate/expert-level, these factors aren't that important to you - if a couple of links are handy they've served their purpose. But you're probably not going to star the repo. It's mostly thousands of perma-beginners who should be opening textbooks and playing with fundamentals in a REPL who are starring this stuff.

[bardan]

I'm furrowing my brow at this one:

"A file is unable to be restored from tape due to several device and media errors. What is most likely the cause?

Media errors usually indicate that the tape media is damaged, or that the tape drive heads need cleaning."

I've read a few of the questions from other categories and I really can't say any of them have been "awesome".

[orev]

You’d be amazed at how many people apply for jobs and lie on their resumes. Sometimes you need some canary questions to weed those people out. They only seem stupid to you because you know the answers.