skysight-inc/HackerNews huggingface dataset:
Depends what you're looking for. None of the prior methods are -bad- if they're what you're looking for. I don't even object to IQ tests masquerading as not-IQ tests; it serves as a warning to me I don't want to work for you.

Depending how many applicants you get, I'd start with a screener, a basic, customized problem that they get an hour to solve, that doesn't have a hard pass/fail, but is just a "Hey, let's see how they code when given a problem". If you have constraints you want to filter for, now is the time (you want speed, see above. You want production quality, give them more time than you think a basic implementation would take, and indicate you want the thing to be production quality; see what they do, what they ask, etc).

If they pass that, yes, what you describe sounds fine, if it's what you're looking for in a hire.

If you want to favor false positives, ask a variety of fairly trivial questions; you're trying to make sure you ask questions they may not have solved before, but which any reasonably competent dev can solve. Bonus points if the person scopes them beforehand.

If you want to favor false negatives, ask harder questions, but make sure they actually are ones you deal with. If you're writing basic business CRUD apps, and your challenges are really in deployment, reliability, gathering and responding to user needs, etc, asking them to implement something from Cracking the Coding Interview is counter to your purposes. Ask them instead what it takes to build a reliable system. Are they familiar with doing that? What are some of the considerations? If they suggest distribution, are they familiar with CAP? Etc.

Really, it all depends what you're looking for. If you want someone who is keen to learn about the domain you work in, ask them if they know about things they have no reason to know about, and indicating that "it's okay if you don't"; see if they admit it. See if they respond with enthusiasm when you start to explain it, "Oh, that's cool!" when confronted with a new idea is probably someone you want, "Huh, okay", maybe not. Etc.

I readily admit, hiring is hard, extremely hit or miss, but a lot of companies seem confused about how it's supposed to work; don't borrow the interview practices of another company in a completely different industry. Google asks those questions? Google -can- ask those questions; they're trying to filter out people. You don't get 1000 applications for every job opening, you can't afford that. You also aren't dealing with the same problems; someone who fails those questions may still be a great hire for you.
My new website: by-a-car-with-a-bro
WebRTC 101
They have an office in Palo Alto. I suspect many of the technical roles will function out of that location.

- https://www.linkedin.com/jobs2/view/14797737
China Attack Aims at Apple iCloud Storage Service
Here's a pretty cool article from High Scalability on it: http://highscalability.com/blog/2014/9/29/instagram-improved....
Microsoft is taking on the cross-platform challenge with Office
This isn't as axiomatic as you might think. Eyeballs count more than revenue in many cases, and can carry some ventures all the way through to liquidity with no profit on the horizon. This is especially true in messaging apps where building a network effect is a far higher priority than profit.
I guess they can, but the wild animals are the primary disease reservoir, mostly just because there aren't all that many ticks feeding on humans and making it back into the wild.

It also matters what species egg laying females feed on. The first few paragraphs of this lay it out:

http://wwwnc.cdc.gov/eid/article/16/3/09-0911_article
I don't think there's a lot of legal hurdles. Companies hire short-term 1099 contractors all the time.
Just a shout to say, if you believe in what the ind.ie guys are doing, then please sign their manifesto: https://ind.ie/about/manifesto/ It's time we valued our privacy one again.
If you want to get a car a 'bro' would like, and you don't know how, then this could be a good idea!
I don't really want to sound off-topic but did you guys get the answer?
beautiful design and great user interface - reminded me of my thesis project on lexical chains.
That is terrifying. I just added this to my zshrc:

git() {
local toplevel=$(command git rev-parse --show-toplevel 2>/dev/null)
if [[ "${toplevel}" == "${HOME}" ]] && [[ "$1" == "clean" ]]; then
>&2 echo "Do NOT run git clean in this repository."
return
fi
command git "$@"
}
thanks for sharing your experience. Did you used persistence features of redis or just the configuration base? like memcache?
pretending to take my joke seriously because you don't like it, cute.
The Perils of Java Schools (2005)
The reason this doesn't work is that most people aren't going to quit their current job for something that isn't a definite offer of full time employment. Would you?
Apps Without Programming? Yes You Can
What Happens When Chemists Don't Wash Their Hands
I agree completely, those operating systems are great, as good or better than GNU/Linux. But with that phrase I was thinking people without prior experience, like Windows users, FreeBSD install is fairly involved for them, there's PC-BSD, but it seems to me, distros like Mint are easier for beginners and useful as a stepping stone to those OSs.
I don't think you can determine what kind of SE/CS you have by whether or not they enjoy (tabletop) puzzles.

I have always enjoyed puzzles (although I rarely do them)--I think it's a part of something greater. I like to complete all the achievements in games. I like checking off tasks in task lists. I like cleaning my plate at dinner.

They all feel the same to me, and have little to do with how I operate as a computer programmer (speaking as a web application developer).
It's a good weapon against Red Hat's proprietary Unix competitors like Solaris - by tying as many things as possible to systemd they ensure it can't run on non-Linux systems. Same reason the proprietary Unices had their own oddball service management frameworks, APIs, etc. Also, RHEL was still using the old, grotty sysvinit-based system where you had to manually specify the order in which services were started and stopped; almost anything's an improvement on that. (All the other major distros had migrated away from it ages ago.)
If there's no news by this time next year I'll probably start to get fearful that they might keep it closed. But it's way too early right now. We're only a month or so after the first public release. As I recall, it took several months for ARM64 to show up, and that was a lot more finished than Swift currently is.
I wonder if their plan for the Indie Phone is to run recompiled iOS apps on GNUstep. Swift would have a lot of value in that case.
The sentence preceding that one reads:

> We literally have not even discussed this [open-sourcing] yet, because we have a ton of work to do to respond to the huge volume of feedback we're getting, and have to get a huge number of things (e.g. access control!) done before the 1.0 release this fall.

If you take Chris Lattner at face value, he is saying the reason the discussion hasn't happened is because they have too much other stuff to do (as opposed to Apple being indifferent or opposed to said discussion taking place).
No, I guess my assumption was that the candidate in this scenario didn't already have a job.
No. Once you agree you are talking off the record, there's no going back on that. In this case, however, I don't think anyone has claimed that Guardian reporters were off the record.

What makes this an interesting case study in journalism ethics is that they weren't off the record, but whether you can ethically act in your capacity as a journalist in the middle of strategic business negotiations. The two are opposing interests, so to the extent I think I'm in a business meeting with The Guardian Company I'm probably also not thinking I'm the lead in their next story.

To turn it around a bit more, would it be OK for Guardian to go into Whisper under false pretenses, knowing they have no interest in a partnership, but in order to gather facts for a story? Surely they are entitled to do that form of investigative reporting, but likewise they shouldn't be surprised if that blows back on them the next time they want to form a strategic partnership with someone.
This will never make the front page, no matter how many upvotes it receives.
You're conflicting things. GNOME doesn't rely on systemd, it wants an API (a few actually, but AFAIK the only difficult one is the bits from logind). The entire API is hard to implement. The parts that GNOME uses maybe can be implemented by someone else. Maybe not. Someone from GNOME tried to do that for FreeBSD but gave up after a while (problem was the lack of interest, difficulty combined with not being a *BSD person). KDE also will use a small part of logind in case you use libinput as well as Wayland. But again it doesn't rely on systemd, it wants a dbus API.

If someone makes something else, go for it. But API wise it is best to stay the same.
I won't even look at contract work. Neither will any of the best people I know. So that one requirement rules out a huge swath of the best candidates.
FastMail is moving to Fastmail.com
Looks like they did a lot of other things at the same time (like not creating app-wide singletons up-front). It would have been nice to see numbers just for rendering.
Could you clarify? I'm confused by what difference does it make what they say.
I thought about it like that : since the one whos cost is 1 is a good roamer he should get each of the other ones? This looks too damn easy?
Jesus. TL;DR:
http://pix-media.s3.amazonaws.com/blog/839/how_tocalculate_t...
What Every C Programmer Should Know About Undefined Behavior Part 1 (2011)
Hi all. If you want to feel better about your worst upgrade experience, I should inform you that mine started : Saturday, October 18, 2014 at 19:00 (local time Greece) and at this time is still stucked in : "2 minutes remaining" :)

Thank you Apple. I think nobody will ever beat this time!!! Not even windows v100!!! I think I'll go for the Guiness Record...
Yep. You noticed that too. I found this out by trying to remove all traces of systemd from my Jessie/Sid installation, found out that I couldn't get rid of libsystemd0 because bsdutils depends on it. That's the same bsdutils that you can't really do without.

It's almost as if systemd was being forced upon you no matter what.
"organisms are constructed in development, not simply ‘programmed’ to develop by genes"

I really wish people who have no slightest idea about programming STOP using the "programs are inflexible" metaphor.

Programs are the most flexible things known to man.

Genes are not blueprints but they are certainly code.
For me it's clearly a deterrent - it does not fit at all into my model of building hierarchies of DSLs.
This doesn't seem like it could have happened in real life. I can't believe someone, especially in tech, could justify working in such an atmosphere with those "benefits".

Yes, big companies may stifle creativity a little, but from what little I read, this startup doesn't seem to be so great..
Ahhhh... seems really obvious in retrospect. Thanks.
Thanks. Maybe our ffmpeg settings weren't creating intra-frames somehow (or we happened to drop every single one) because the stream would never recover. I'll probably try it again at some point soon. We really want jsmpeg to work.
Privilege Escalation on Windows 8/UEFI Systems
So true; the Google, Facebook, Microsoft, Fill in Here puzzle interviews are pretty silly. Rather than splitting people into groups of "good developers" and "bad developers" they can really be split up into these two categories.

1) People who read Cracking the Coding Interview
2) People who haven't heard of this book.

http://www.amazon.com/Cracking-Coding-Interview-Programming-...

Seriously; any competent programmer can crank through the stuff in that book in a week or two and be solid for the types of silly questions they will be asked in those interviews.

Honestly the best interview I ever had was one where I interviewed with a highly technical IT director and it was just very conversational. We spent about two hours of just chatting about the different types of technologies we had been working with and kept diving deeper and deeper into knowledge areas. At the end of it he just says, "Ok, you are obviously a smart guy; I'm going to send you over to see the VP now so you two can discuss salary requirements."
Big is over 1000 pages of a spec.
FedEx Tech Manager
Ultimate Front End Development Setup
So, again we have Lattner saying that Apple hasn't even considered releasing it as open-source. Still not seeing the part where Apple is going to open-source it.

Also, he said they have stuff to do before the release this fall. That happened, and still not a word about it. I don't see how you can possibly take this "We haven't even talked about it and I can't say when we will" as a declaration that Swift will be open-sourced. It is the opposite. It isn't a firm denial that it will ever be opened up, but it is definitely a denial of any plans to do so.
Sometimes I wonder if it would make sense for investors to send someone they trust to apply and interview for a position at a company they're considering.

If what she wrote is accurate I don't really understand how they managed to raise $30 million in funding.
Cryptography Methods to Guarantee Payment Anonymity
It's at the top of the front page.
I think the fallacy is looking at the composability of tools on the command line and thinking you want/need the same composability in how the system runs. You don't. The Unix Way is actually TWO things: one is shellscripting and the composability of the command line, and the other is C and libraries. "Whipupitude vs manipulexity", to quote Larry Wall. Systemd is the result of determining that running system services is complex and needs to be handled by a real program instead of scripts. This is easier in C, but the flipside is the unavoidable loss of whipupitude. For most people this is fine. When Unix was young, whipping up something simple was fine. Now it isn't, and really hasn't been for quite a long time.
Interestingly, so far people preferred to implement dialects of Lisp-1 mostly. Not that many Common Lisp subsets or even Common Lisp-inspired languages around. I can only name Shen as one obvious exception from this rule.
For Peer Lending, a Change in Financing
Turns out 500-pieces puzzles are more like an exercise in banality and less like actual puzzles.
Wow, this _open letter_ is so full of nerd rage that it fails to capture any of my sympathy. I expected to see a humble effort to create an open-source Swift compiler that would move the conversation forward. Instead, I'm left feeling this effort is out of spite alone. All of this before Apple has made any final decision on the matter one way or another.

It would be really cool if the Swift compiler would build code for both Windows and Android so we could have true portable software in a language that isn't C or C++. So I'm hopeful the Swift engineers also see value in that. Though right now it's a language that's so tightly tied to Objective-C and Foundation that I suspect it will be a very long time before we see that come true.
The Time article is actually a very dry summary of the study's key finding, written in colloquial but not sensational language. It also has a link to the study in the very first sentence. I found the full text very easily: http://www.chc.ucsf.edu/ame_lab/pdfs/Leung%20et%20al%202014a...

The poster above could easily have satisfied his/her own curiosity on this point. 'Did researchers control for [extremely obvious thing]?' is becoming like 'correlation is not causation' - a smart-sounding thing to say instead of going to the effort of engaging with the material. It only took me 2 minutes to track down the paper and find that the covariate factors are discussed in detail over a full page of the paper.
HFCS is equal parts fructose and glucose, same as sucrose.

Lustig is an obese laughing stock and derided by real nutritionists.
yea, I had bad experiences there too. They are very bad with hiring contract. Really treat employees like bad
While it would be technically considered contract work, I think its a little short sighted to forgo a trial period because of what they called it. Its hard to see if an office would be a good fit in an hour or two, so I think the extended interview would work well.
All I want to know is if I can drink a diet coke a day with impunity.
And also to a place where no one will judge you because you're a nerd. My CS classes where pretty gender-balanced, more so than my high school, and I can assure you that's not the problem.
Url changed from http://modernfarmer.com/2014/10/plants-can-tell-theyre-eaten..., which points to this.
Who cares what the range is? You can detect distance of the device before communicating. And do you think the data is not encrypted?

"Wifi has too long of range; don't ever purchase something if you're on wifi!"
This is probably hard for most engineers to relate to, unless part of your role is doing support.

edit: when I say something is not insane or unexpected, I mean it in the context of a person looking for work in customer support. These are the things you run in to. So if you are shocked that they have to provide their own hardware, then you are shocked at the way support people are often actually treated. I'm not advocating for or supporting that.

The interview process and criteria for being hired have really high variance compared to engineering interviews.

The author of this piece made the classic, and often unavoidable mistake of being between a rock and a hard place and not vetting the company she interviewed at and ultimately worked for for a day.

Even if you're not an engineer/designer/data scientist (or one of the typically highly desired people for a startup), you should be working at places you love and believe in, when you're not, you end up having bad experiences and those bad experiences are amplified by the environment.

First, I didn't find Ajay's interview to be that weird, saying why you came up with the idea for your company and your qualifications should be expected, not interpreted as a way for the founder to diminish the potential future employee. If you don't believe in your leaders, and don't trust them, you are in a lot of trouble.

edit: I think that not having interviewed with the actual support team members is a huge red flag here as well, but owing to the author's somewhat desperate situation, they moved forward anyways.

12 hour days is insane, and wrong. Having to provide your own device is not really that insane for small teams. Obviously it's great if a company provides it, and probably larger companies should always provide a workstation, but this doesn't come across as totally abnormal. The constant "want to hear a joke" and racist/sexist tone at the company is also not acceptable, but clearly was supported by the people working there at the time, if the anecdote is taken at face value.

It's super easy to pay for a trial period, and as far as I'm aware, it's not even legal to have people work for free unless you are a nonprofit or government organization, so that's shady, even if only for one day. I've done two week trials that were fully paid, and it was a great way to get a feel for the company and vice versa.

Not having any onboarding, given that the trial was for a day isn't too surprising, but that is clearly a problem with a one day trial. They should have absolutely been given some lead-in material to help them get prepped before starting.

There appear to be a lot of growing pains at Handy, which isn't a surprise, but hopefully they can move fast and get their support/service wing to be as tight and focused as the rest of their team (assuming that is true).
Agreed, Monty's articles and videos are phenomenally educational and well worth the watch.
"I mean it's like the celebrity A list in a sense."
Well... they let me in, and I'm as far from being any kind of celebrity -- I'm truly the most ordinary person anywhere.
And I'm pretty sure that I'm not in the usual demographic for a site about new tech products. I like to think that I offer a mature and wise perspective. But really, I just like to learn about tech. :)
Ttyrec conversion
It's also a serious issue in New Zealand. It's exacerbated by children running around with sippy cups which allow constant contact between teeth and juice (or worse, sugary drinks).
I will add that if you're using Docker (which we weren't) it might be easier to deploy a new set of Docker containers with updated code and just throw away the old ones.
If people actually expected that, then it was just silly of them. Even if Apple were completely committed to making Swift open source (and I'm hopeful they are), I wouldn't expect anything to show up for a couple more months at the least. Apple often takes their time open sourcing new stuff.
I really liked this site!
To be pedantic, life is the most flexible thing known to man.
Customer Service as Reality Distortion
I'm actually not aware of any advancements being made in JS that haven't already been made on other platforms. For example, the JVM is much more performant than Node, has more libraries, better build tools, better development environments and so on.

I also think that other languages are more flexible and productive. JavaScript is a very crufty language with a lot of gotchas and odd behaviors. Dealing with these wastes developer time and makes large projects harder to maintain.

I'd much rather work with a language like ClojureScript and have the benefit of using the same language on the client and the server, while using a well thought out language.

Writing apps in ClojureScript is far more pleasant than with JavaScript. There are also fantastic libraries available such as Reagent (http://holmsand.github.io/reagent/) and Om (https://github.com/swannodette/om).
Cooperative concurrency is fine and a lot of languages use cooperative concurrency just fine. The issue with Node is that it completely ignored the multicore reality that we live in. Everyone argues that multithreading is so complex, and it is unless you have the right abstractions. But what is guaranteed to always be complex is single-threading with process forking. As soon as you want to communicate between processes, and you will want to communicate between processes, you now have to implement IPC. In come the message queues... that is once you pick which message queue to use.

We've also been using event-driven IO for decades and Node is the only modern run-time to ignore the obvious perils of evented IO. Instead of doing what languages like Go and Erlang did, which is have event loops in the run-time that are completely transparent to the developer, Node pushes the evented IO right into the application developer's face. Are there remedies for writing good evented code? Absolutely. But why should application developers need to be schedulers in the year 2014?
This libsystemd points to a dangerous habit of the certain group of developers who prefer strong interdependency and monolithic architecture. In similar way, you have libdbus which is technically not the actual dbus, but tries anything to launch dbus processes if loaded and initialized as a library. And gconf libraries which ship daemon executables and also launch daemons from library. Libsystemd is apparently not doing such right now, but given its windows.dll like nature, it's a reasonable concern to have.
This is pretty bad. I'm debating whether it tops the job where I got fired for speaking Spanish, but it's bad nonetheless
Tooth decay is caused by vitamin and mineral deficiencies, not sugar consumed during meals. Orange juice and other fruit juices are excellent sources of vitamins and minerals.
Yikes!

I honestly can't tell if you're being sarcastic or serious.

Childhood obesity is a serious issue. Heck, even type-2 childhood diabetes is a growing concern.

Do you have any support at all to justify this claim?