Hacker Newsnew | past | comments | ask | show | jobs | submit | more lambda's commentslogin

That's 677 total puzzles. But remember, it says that there are in total 11 areas, of which you need to complete 7 or 8. And it says that to complete an area, you don't necessarily need to solve every puzzle within it.

So let's say you need to solve, on average, 75% of the puzzles in an are to beat it. And that you need to solve 7 out of the 11 areas. That gives you (677 * 7/11) *.75 / 40 or about 8 puzzles per hour.


When you say "this site", please include the actual site that you are referring to (edit: like "mkweb.co.uk", rather than "this site" or "the site of the current URL"). It is hard for others to tell if a comment like this is actually referring to the current article, or it has subsequently been changed. Edit: this applies to people other than mods here too. In general, if discussing the title or some aspect of whether the correct source was used for the news story in question, please quote the title or include the name of the site you are referring to, as otherwise a subsequent change by the moderators can make your comment nonsensical.

As a note: I really wish that HN would include a history of title and/or link changes for an article, so that when you go to a thread an people are complaining about some problem with one of them (or are reading the article with an interpretation based on the old title), it becomes easier to tell what they were referring to by checking against the history. As it is, in a large number of the cases in which a title or link is changed, a large portion of the discussion no longer makes sense as it was referring to the old title and/or link.


Agreed. Later, if dang gets his better url, his comment might read "17 hours ago" "the site of the current url" and we'll be thinking some proper source ripped off the content.

All of the solutions are sub-optimal, but preserving a history would be nice, at least.


We wouldn't change the URL again without updating my comment about the URL change.


humans err. it's why we have version control. but good to know your intentions


Note that high-reputation users can see deleted questions and answers on SO, and petition for them to be undeleted. So there is at least a check on the ability of the moderators to delete things for personal reasons.

Most of the complaints about deletion or closing on SO are not about it for petty personal reasons, but instead a general community mindset that is a bit too quick to jump to closing imperfect questions, questions that are close to duplicates but not quite, questions that are somewhat subjective but still have a lot of users interested in them, and so on.


>> Note that high-reputation users can see deleted questions and answers on SO, and petition for them to be undeleted.

While overall, SO's a great place to get questions answered, the problem, in my mind, is that there might be a disconnect between the high-reputation users and newbies who asked and the newbies come to SO to find answers to the questions that do flagged down or deleted.

While I don't think that any of the high rep users are newbie haters, I do think it can be challenging for them to see things from a newbie's point of view.


In my experience, the standard newbie questions have all been answered. A quick search is all it takes to find the answer. The problem, of course, is that newbies rarely know the right questions to ask (read: search), which is to be expected because they don't posses the right amount of domain knowledge.


>> The problem, of course, is that newbies rarely know the right questions to ask (read: search)

When I'm "learning a new tech" -- let's use switching from Rails to Node as an example, I usually go to Google first.

Ask a question like "why would I choose Framework X over Y" in Google's searchbox, and your top results will have the same question on SO, except that it has been closed because the answer is opinion-based. The few answers to the closed question are usually fairly objective and insightful and leave me wishing that more people were able to add their 2 cents.

Sometimes newbies ask a broad question to get a big picture perspective (from multiple people answering) that can't be provided by a couple of blog entries found in Google results. And yes, those questions might elicit opinionated responses, but I would argue that the responses add more value to SO than they take away.


Ah, if your problem is about opinion questions like that, I recommend you not try to get StackOverflow to support that. StackOverflow is specifically geared towards objectively answerable questions; solving an actual problem that can be solved by code. "What's the best framework" or "why is framework X better than Y" will never fit well into its model.

I recommend starting another site, tailored for that kind of question, if that's something you're interested in. I imagine it would look pretty different than SO; instead of simply sorting by votes, you'd want to group answers by "reasons to prefer X" and "reasons to prefer Y", each of which could be voted on, and with optional discussion threads to clarify each one of them, or something of the sort.


>Ask a question like "why would I choose Framework X over Y" in Google's searchbox, and your top results will have the same question on SO, except that it has been closed because the answer is opinion-based. The few answers to the closed question are usually fairly objective and insightful and leave me wishing that more people were able to add their 2 cents.

They are often very outdated too - some were closed 3, 4, 5 years ago and never updated.


>> They are often very outdated too - some were closed 3, 4, 5 years ago and never updated.

This is true, but closing a question pretty much guarantees that it won't ever be updated.


I don't really think that you're right that high-rep users can't see things from a newbie's point of view. Most high-rep users got there by being good at seeing things from a newbie's point of view, and thus being able to explain things well to newbies.

The answers that get the most upvotes, and give you the most reputation, are the basic problems that everyone has, since then everyone finds that question, and upvotes the answer that solves the problem for them.

I'll note that as a high-rep user (top 0.1% overall), I more often see the moderate-rep users as the ones closing a lot of questions. The high-rep users are busy getting more reputation by actually answering questions, it's the moderate rep users that have just enough to be able to vote to close that wind up spending all of their time policing the site.

The biggest problem that I have with SO is the review queue, which queues up questions that have close votes or flags, in order to get a quicker resolution, and rewards people with badges for spending a lot of time reviewing questions that they don't really know much about. I've seen so many slightly vague questions closed because of that, when if you had actually just spent a few minutes getting the user to clarify via comments, you could have figured out what their actual problem was and answered it. But because there's a review queue, and badges for reviewing lots of questions, answers, edits, etc, some people just spend all their time in there rather than actually trying to answer or clarify.

Anyhow, I very frequently hear vague complaints about SO, but it's much more informative to look at particular examples. Do you have examples of questions that have been closed that you don't think should have been? As a high-rep user, I can vote for them to be re-opened, and as an experienced user I can help reword them and make them more clear so that they will be more likely to be reopened and less likely to be closed.

By the way, one thing that can be challenging is figuring out, from a question that doesn't provide enough information, what the user is asking. This is hard for anyone to figure out, newbie or experienced user. The best way to avoid this is to ask questions clearly. State the exact problem you're trying to solve, show a small code example that demonstrates the problem, state what you've tried in order to solve it. And state a question that can be solved objectively; there's no way to provide a good, unambiguously correct answer to an opinion question, and the whole reason for StackOverflow to exist is to provide good, unambiguously correct answers, not to prompt endless discussion threads in which everyone discusses their favorite X.

If you follow these guidelines, you should generally be able to get a good answer on SO, and not have your question closed (unless as a duplicate, which is another way of solving your problem by redirecting you to existing answers).


> Yes. My experience of hiring is that it is extremely hard and imprecise. I prefer to give the candidates every advantage possible.

Yes, I agree that hiring is hard and imprecise. I generally try to ask questions on a variety of different topics, to make sure that I can find where their strengths are; if they are weak in one or two areas, that can generally be worked around, but if they come off weak in 3 or more of the areas, I generally feel that it would be too much of a risk and take too much time to bring them up to speed.

> I would help them to the extent of my abilities in a work situation, so I see no use in being unnecessarily difficult in an interview

Do you really consider this question unnecessarily difficult? I find that it's one of the easiest, that someone without even programming knowledge but with a good technical background should be able to answer.

> I know many highly able programmers who wouldn't know how to respond given so many options

If someone doesn't know where to start, I give them a prompt; "just focus on the networking level". If they start but miss something, I ask a follow up question to clarify that "so how does it know what IP address to contact?" When I ask a question like this, I'm not trying to be tricky, but trying to ask a question that should involve knowledge that just about every competent programmer should have, and see how well they can break it down, explain it, stop at the part where their knowledge runs out rather than making things up or guessing.

I've had people guess on this question, completely getting it wrong when I ask something like "and so what is the difference between TCP and UDP", and I find that even worse than just saying "I don't know how that part works"; if someone knows what they don't know, they will know when to ask questions, but if they just make stuff up to try to make themselves sound more knowledgeable, I don't know if I could ever trust their knowledge or judgement because it could be based on them just covering up a lack of knowledge about something.

> Everyone talking about it showing what you're interested in is 100% wrong in my case. I am not interested in TCP, DNS, etc. I know the details because at some point I've needed to debug something at that level.

Yeah, I don't ask this question to tell what someone's interested in. I ask it to determine (a) if they have enough experience that they have done at least some looking into how the stack works enough to discuss it intelligently and (b) whether they are capable of breaking down and explaining a complex piece of technology with several interacting parts.

For the jobs I'm hiring for, understanding the basics of how the network works is pretty much a requirement. If someone doesn't know how DNS and TCP work, asking them to debug a complex performance problem with a distributed filesystem communicating with dozens of clients over a 40 G backend network and 10 G frontend is probably going to be asking a bit much of them. Even for the more basic application development tasks, almost everything we do touches the network somehow.

And if someone does actually discuss the details of input getting from the keyboard into the kernel, and from there into the browser, and it handling the event, and so on, then that does provide me with information that they know that portion of the stack well; I don't expect everyone to know everything, but I do want people who are interested enough to at least have some basic knowledge of how the fairly complex system that they use on a day to day basis works.

> > Yes. My experience of hiring is that it is extremely hard and imprecise. I prefer to give the candidates every advantage possible.

Yes, I agree that hiring is hard and imprecise. I generally try to ask questions on a variety of different topics, to make sure that I can find where their strengths are; if they are weak in one or two areas, that can generally be worked around, but if they come off weak in 3 or more of the areas, I generally feel that it would be too much of a risk and take too much time to bring them up to speed.

> I would help them to the extent of my abilities in a work situation, so I see no use in being unnecessarily difficult in an interview

Do you really consider this question unnecessarily difficult? I find that it's one of the easiest, that someone without even programming knowledge but with a good technical background should be able to answer.

> I know many highly able programmers who wouldn't know how to respond given so many options

If someone doesn't know where to start, I give them a prompt; "just focus on the networking level". If they start but miss something, I ask a follow up question to clarify that "so how does it know what IP address to contact?"

> There are much simpler ways to discover 'basic competence'. Getting candidates to translate a basic algorithm to pseudo-code even.

Yes, you would not use this as a sole interview question. This should generally be used as one of several. My basic screen consists of: write up a basic algorithm in pseudocode, compare and contrast data structures and running times for a couple of basic tasks, the "what happens when I enter google.com into my browser and press enter" question, a question on designing a class hierarchy for modelling a particular problem, a question on debugging where I lead them through a problem I've actually had to debug and see what kinds of suggestions they make about things to look for and ways to figure out what's going on, and then an actual coding problem where I expect them to provide real code to solve a simple problem.

I don't expect everyone to be an expert on all of these. Some people haven't ever taken a formal algorithms and data structures course, or it's been 20 years since they did so, so they haven't really thought about asymptotic running time in a long time. That's OK, as long as they do well on the others. Or some people may not know much about networking, but are strong in the other areas; that's fine too.

But if someone doesn't know much about networking, or algorithms, can't design an appropriate class hierarchy and interface, and can't really offer very good suggestions for how they would debug a problem that we encounter variations of fairly often here, I wonder whether they really are going to be able to contribute effectively. Or if they can talk a lot about the data structures and networking, but then fail at actually writing pseudocode to solve a basic algorithmic problem (and I'm talking very basic, like you should be able to do this in a CS 101 class) or fail at actually producing working code for the simple coding problem, I feel like they may have some good domain knowledge but don't actually have the skills necessary to actually contribute.


I'm curious how long your screen generally lasts. In my hour-long phone screens there's barely enough time to cover a coding question and a few basic data structures/knowledge questions. I feel like covering everything you laid out would take several hours.


I try to keep it within an hour, but sometimes go over, up to an hour and a half.

I usually have the final question, writing real working code, be something that the candidate does offline using a real editor and being able to test it out, and email me the result afterwards, as we're usually low on time by that point and many people are more comfortable doing that in a real editor, being able to test out their code, etc. However, it turns out that the last question can be done as a one-liner shell script (it has one little tricky bit that make the simplest one liner shell script you might write not quite work properly, but it's possible to work around that), so some people are able to just do that online with me during the screen.

I generally keep the screen moving quickly, giving people prompts and hints to get past parts they're stuck on to keep things moving, and when I say I'm asking basic questions, they are really quite basic. My experience has been that people who actually pass the screen generally complete it within the hour, while people who are struggling are the ones who take longer.


Well, Rust is now at 1.0.0 alpha, which means that the language has almost all of the planned breaking changes implemented (there are still a few corners where there are a few breaking changes planned, but in things that are minor enough to be unlikely to break much code).

The standard library is still in rapid iteration mode in the preparation for 1.0.0 beta, and thus large portions of it are marked unstable and so only available if you opt-in via a feature gate, but the plan is to stabilize that through the alpha and beta period and have a usable, stable standard library at 1.0.0, which is planned to come out within a few 6-week release cycles from now. And things which are not ready, or not really appropriate for a core standard library, are being moved out into separate Cargo crates that can iterate independently from the core language.

So yes, Rust has been iterating rapidly on the road to 1.0, which makes keeping up with the treadmill painful, but it's finally settling down; very soon you should be able to use it without constant breaking changes.


> in things that are minor enough to be unlikely to break much code).

As much as I want this to be true, it's not. `io` is one of those libraries. That's going to break a lot of stuff, probably.

Beta is the 'your code will almost absolutely not break' release.


Sorry, tried to make that distinction by saying that the language has very few breaking changes left, and those that are left are expected to be minor, but the standard library is still in rapid iteration mode and is expected to break a lot.


It definitely caught on in some circles; I've seen a number of other blogs that contain a badge with this emblem. Hasn't by any means become universal among hackers, but isn't a complete flop either.


I ride a Brompton, and that is one of the big reasons; I can just take it inside, and stash it under my desk, rather than having to lock it up outside.

However, it is inconvenient in some situations. When I go to a bar, or restaurant, or movie theater, it's sometimes hard to find a place to put it that's out of the way. Since a lock is cumbersome and inconvenient, and I don't usually need it, that means I don't make a habit of carrying one, but then I'll hit a situation where it really would be more convenient to lock it up than take it in, but now I don't have that option.

That said, I do ride my Brompton as my daily commuter, and do bring it in with me, and most bars, restaurants, or the like do have enough room for me to stash it somewhere. But you do have to be willing to put up with people who think it's a little strange, or the people who joke "hey, I don't try to bring my car into the bar", and you do sometimes need to be creative to find a way to stash it securely and also out of people's way.


Has anyone (Mozilla, Yahoo, SUSE, Netflix, Facebook, Github) filed a counter-notice yet? That's the next step in the DMCA dance; if you file a counter notice, and the accuser does not then file a lawsuit, Google can put back the content.


In Firefox 34.0 on OS X, both Incognito Mode and clearing history from the past hour appeared to defeat this attack.


Number of lines of code can be used as a (very) rough metric for complexity; expressing the same application in more lines of code may mean that the new implementation is a bit more complex, harder to work with, more to review, etc.

Of course, this is quite a rough metric; some languages are much denser per line (like APL/J/K and others in that family), so it's definitely not an absolute rule. But it can be interesting to compare a direct port of a reasonably complicated application from one language to another, to see how the abstractions in each language hold up; just like it can be interesting to compare the speed when porting from one language to another, even though there are plenty of caveats there too.


Lines of code is a pretty poor measure of anything except lines of code. More lines could be more clear or less clear. Unless we're talking an order of magnitude, which seems unlikely.


> Number of lines of code can be used as a (very) rough metric for complexity

When the code is a port and represents 1:1 functionally, then line of code is totally irrelevant, except for it's performance to execute (which clearly GoLang has demonstrated in this case to outperform ruby). A better "rough metric" for complexity is the number of functions or as Ruby Flog puts it - ABC metric: Assignments, Branches, Calls.[0]

[0] - http://ruby.sadi.st/Flog.html


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: