skysight-inc/HackerNews huggingface dataset:
And therein lies the problem, these "consumers" are consuming what exactly?

The pressure to please "consumers" is too strong, and this leads to putting all the risk on the "producers" side. Which means Kickstarter will be nothing more than a weird and sucky version of Amazon.
Perhaps the interviewer could work on the job you had to take PTO just to go to the interview. Then you can assess his skills and just say you were WFH. Fair trade?
Firstly, I think they wanted to 'assess' not 'asses', well at least I hope so (spell checking is not optional; even on a blog).

Now, I agree with the blog post: if you want me to code at interview it has to be open source, pseudocode or a toy library. Not your production app. I don't want to see you proprietary code till I am hired in case some moron on your staff later goes on a spree suing people on an open source project where the code looks 'similar' to what they may have seen in your code-for-free cheapskate interview process.
I don't see what the problem is: it's clearly not work for hire, and he doesn't mention any explicit copyright assignment. At the end of the day the candidate retains copyright, and the company has no right to the changes.

(Of course, the idea of a day-long technical interview exercise is truly insane.)
Do i sound like I would care?

Give me a way of watching what i like the moment it comes out (not 3 years later) and I'll pay for it.

Otherwise I'll do whatever it takes to get it.

There's still series that I watched and enjoyed over 5 years ago that are still not translated and sold outside of japan so should i waste my tine waiting for a miracle because of the Berne Convention?

If the market is not willing to do it the community will plain and simple.

The problem is at the moment the community is a lot better at offering what people want then any company.
I understand the reluctance to work on the production code for an entire day. But like others have commented, I would rather do that and get a chance to see their end-to-end process rather than coming in on the first day and finding their dev environment is a complete mess.

I've come in as the new guy on a project and been greeted with a zip file of the code base (already out of date). It was complete with hard links to the main developers personal test database running on his machine.
Wonder if they have a licence for Helvetica used in the banner.
Try again, I'm using my HP Minilaptop with AMD components on (X)ubuntu or Linux Mint, 32 inch samsung is detected better in Linux then it is in Windows. (automatically runs it Full HD compared to Windows' 1366x768 )
It's interesting. Putting aside the actual value and concentrating on the behavior. If a driver knew that a school keep gasoline for filling up buses or other purposes and went and topped up his car while his son played tennis he/she would be fully aware that they were stealing. They may still do it, but it wouldn't make the papers and/or they wouldn't act surprised if they were caught "Oh can't anyone take the petrol if they need it?"
These are easy things to ask directly without working for free ;)
What do you do with all visitors coming from old and broken links ?
> A simple implementation that solves any of the NP problems in polynomial time is a much better proof than any article.

That completely misses the point of P vs. NP, which is not about programmability but a problem entirely of theoretical nature (and interest).

- O(n^<Graham's number>) is in P. (If you can solve TSM in that time, you've proven P = NP.)

- Cracking AES-256 is even easier than P: it's O(1).
Introverts & extroverts: productivity methods for each personality type
But who offers to do a technical test for the entire day? For me, any interview going longer than an hour has some serious issues...
Oh the theoretical aspect is important.

But applying it is important as well. Of course, most quantum computing algorithms have not had a chance of being implemented; it's not always possible

Or, as Knuth put it "Beware of bugs in the above code; I have only proved it correct, not tried it."

But if someone comes up with a paper showing a new algorithm but doesn't come up with an implementation of it when it would be straightforward to do so, I begin to doubt this person.

Most other fields don't have the luxury of easy testing.
I wonder how the copyright situation would be if you were to write code during your interview that they continue to use. That's before any sort of contract that details what rights the company has to your work (since they cannot take your copyright they usually reserve all other ways of using it). So technically that's still your work and you have full rights to it.
"It is better that ten guilty persons escape than that one innocent suffer"

That was said in 1765, I think we are regressing. Power hungry police and prosecutors are getting worse. They only care about making arrests and getting convictions, innocence doesn't matter. I am surprised that the prosecutor was actually charged and then convicted.
So here's the problem:

1) A great way to assess your technical chops is to watch you code.

2) A great way to see if you can do the actual work that you'll be expected to do on a day-to-day basis is to work on a real-world task on the team's actual codebase.

3) If you have what it takes, then it's crappy to have you "work for free" for a day. But if, after the day's over, it's clear that you don't have what it takes ... then have you really "worked for free"? (Remember, freelancers don't get paid unless they deliver.)

Here are some ways to address this problem:

1) Do paired programming on the actual codebase -- but on an old problem, the solution to which has already been implemented in production. This makes it clearer that the exercise is merely to assess your skills and not to get free labor out of you.

2) Pay all in-person interviews for their time. Once they've passed the phone screen and whatever other preliminary hurdles you've set up, you should feel pretty good that they're not just wasting your time. So compensate them.

3) If you don't have the budget to do #2, which -- let's face it -- is uncommon, then perhaps you could offer a signing bonus to anyone you end up hiring that essentially repays them for their time.
In my experiences much of what I considered "imperative code" could be written in a functional manner more easily in the functional host language, though the solution was usually very conceptually different.
The suicide is hardly beside the point.
Please do note that the author is Kevin Poulsen and he writes:

"His jury trial was looming when Swartz took his own life in January, 2013.

MIT faced a firestorm of criticism in the wake of Swartz’s suicide. Critics, including Swartz’s family and prominent MIT alumni, said the institution betrayed its own principles by not advocating for less harsh treatment of Swartz."

I can't see how "undid" would point to anything other than his "not being here". His presence being undone. His life being undone.
If he would have been incarcerated for life, I don't think Kevin would use the word "undid". He would print "Free Aaron" stickers, and getting the word out that this fight should not be over.
Calls for transparency
In short, mostly. Full 4.1 support in Mavericks: http://rk.md/2013/opengl-osx-mountain-lion-vs-mavericks/
Agreed, this presentation seems to be more of a 'shell 101' than anything else
I'd like the web to move to SRP [0], or, since you should be using tls if you're accepting passwords anyway, TLS-SRP [1].

This way noöne, not even your email provider, actually has your password.

[0] http://en.wikipedia.org/wiki/Secure_Remote_Password_protocol

[1] http://en.wikipedia.org/wiki/TLS-SRP
Not sure what you mean by "memory requirement" and "theoretical time". If you don't access the memory, what do you mean by saying you "need" it?
If a turing machine — or a computer program, for that matter — uses, i.e., "visits", exponentially many memory cells, then, indeed, its computing time cannot be polynomial.
But note that every turing machine theoretically has infinite memory. The question is how much of it is actually used. PSPACE consists of those problems that can be solved by a turing machine that uses no more than p(n) memory, where p(n) is some polynomial in the input length n. Note that, for PSAPCE, time is unrestricted. So obviously P and NP are subsets of PSPACE, but it is unknown whether they are proper subsets.
Did Gabe and Gates write any substantial code? At least lately? I don't think we could relate them.
Slightly (only slightly) off-topic: what is it going to take for us to see a complete or at least large overhaul of the justice system in the US? We're incarcerating too many people for minor crimes and it is causing a ripple effect on poverty and economic growth (not to mention ruining TONS of people's lives).
You can [1] create a transaction that destroys those coins (spends them on fees, sends them to a charity or really takes them out of circulation) at some time in the future (using nLockTime [2]) in such a way that it could be replaced with another transaction before that time (using a low sequence [3]).

[1] In the future, its not all active yet

[2] https://en.bitcoin.it/wiki/NLockTime https://en.bitcoin.it/wiki/Protocol_specification#tx

[3] http://bitcoin.stackexchange.com/a/2032
The obligatory vfio qemu link.

https://bbs.archlinux.org/viewtopic.php?id=162768
IANAL

You're right you'd own full rights to your work. That doesn't make a difference though - you'd realistically never sue them.
Regarding solution (2) it is probably that you should offer to pay for their time. Many people can't accept paid work under their current contracts.

Also whatever the plan if the interview is going to be for more than a couple of hours let the interviewee know the rough plan in advance.
any ideas on what frameworks/technologies were used to build this?
Shell access used to be a standard part of all ISP accounts. If you go back far enough, there were no standards like PPP and SLIP to extend TCP/IP to dialup customer computers, and no graphical clients for internet services, so to "get on" the internet, you needed a shell on your ISP's systems.

Your ISP might have existed back then, or been founded by someone who did, or had customers who expected the service.
A dummy project is your best bet. It provides a nice stable fixture from which you can gather repeatable data, and you can tweak it over time as you discover flaws in it.

If you're already employed, you're probably taking a day of vacation or sick time. So you're being paid. On the other hand, you're losing a day of vacation or sick time. This has been true for years and years (but that doesn't make it right).

Frankly I would seriously worry about trade secret exposure, and any restraint against "moonlighting" or competition by your current employer (some employers forbid working on open source as well). Working on live code puts both parties at risk here.

There are indeed companies where, if I had worked on their live code, I would never have worked there (one company was where I learned the phrase "train wreck").
Don't forget the 4'th group, the class of programmers who refuse to put code on github.

I've gathered there is a population of "developers" who refuse to demonstrate the ability to code at any stage of the interview process.

(The OP is definitely not part of that crowd, given his willingness to submit a pull req to some open source project.)
The House is really worried about 3D printed guns. So it’s voted to ban them.
Cool, could you hint me which version(s) of (x)ubuntu and mint are working out for you? I couldn't get passed the Mint login screen after installation. Couldn't drop to tty either. System froze over :(
I'm now on ubuntu 12.04 which seems better, but still.. HDMI/dual monitor is bugging me out.
In most cases (distinct HR department) the HR guy doing the interview will have no idea what processes the IT department uses.

Worse case, the HR guy is actually a decent IT guy (so that the IT-related questions in the interview are actually fair), but he has multiple different IT departments which each use different operations policies so he can't answer your detail question. Happens especially in bigger companies or, as I experienced, in government.
I agree here, but I wonder if it'd be kosher to pair program on an open-source project...that my team totally intends to incorporate into our closed-source product?
4) Do paired programming on an actual feature or problem for an hour or two. Work with your potential team members and discuss the feature, do some rapid prototyping etc.

The assumption isn't that your code will be deployed at the end of the day, but that both side will get to see how the other works and you don't waste too much of anyone's time if it's not a good fit.
> even SVN is something I'd like to have a night of good sleep before accepting.

Why's that? SVN may not be fashionable, but it's centralised, has ACLs and a hook system.
I was thinking this as well, minus the HN part. It is similar to what eBay sellers would do with a hot auction. Jump in on the bidding with a second username and run the price up to where either a) someone else outbids them or b) they find the highest bid, retract the bid and then bid right under the highest bidder.

Same scenario with Kickstarter. One could set an ideal funding point and run it up with fake fundings. Catch the attention of media and then hope that the bandwagon happens getting them more than what they are asking. Once funded over the amount, back out your fake fundings and voila - funded.
Well, it actually is different comparing a freelance graphic designer to a fulltime developer.
The code was going out at the end of the day. Whether they had the copyright or not, they clearly intended to use it. What's he going to do; take them to court over it?
The last place I interviewed with set the bar pretty high as far as I was concerned.

After a pretty standard interview one afternoon, I got asked if I'd be willing to come back in for a couple of days to see if I got on OK with their current team. They made it extremely clear that as they'd be taking up a couple of my days, they'd pay me pro-rata for them whether I got the job (and chose to take it) or not.

If you're interviewing with a company that actually cares about the happiness of their employees, then they tend to make this pretty obvious pretty quickly. I would suggest that the ones who make it obvious are the ones you want to be working for.
My point as the GP entirely.

You can only hold a prosecutor to a "perfect standard" if they have the power to ruin a person's life through self-interest. That perfect standard should only be enforced the other way as well in the circumstance that they do something wrong on this scale.

These positions attract people who wish to be wealthy or powerful. This might not be the case if they have to live up to their own standards.

Examples should be made of both sides.
You have variants in:
the HTTP method, the URL path, the URL query params, various HTTP Headers (cookie, content-encoding, content-language, ...), the Body (with various forms of content encoding) , did I miss something ?

If you think of a request as a function call then it's all parameters and it's completely crazy.
And not to mention enriching some people through wrong means.
Which makes me wonder: how do you filter these? In physics it's common practice to ignore papers about Perpetuum Mobiles (excuse the probably incorrect plural), but here we have a topic that is somewhat easy to write good and bad about while still having very high relevance.
> If the same story had happened to a graphic designer then most would agree,as usual in that case, that you have to set limits and not work for free "just to see what you can do".

On the flip side, literally every interesting answer that you give folks in an interview process could potentially be considered to be free work. I used to work on recommendation systems. Say, I go interview at another company in the same space, literally any potential what-if machine learning problem can eventually get into the situation where it goes off text book fairly quickly. At that point, any information that I talk about has two values: 1) it helps the people understand that I can do this shit. 2) it also helps them maybe solve the problem based on my experiences from my previous job. In the case of 2), they are essentially getting free work. How do you resolve such a situation? Should we have an industry wide standard where people pay you a market rate for every hour you interview?
That's presumably a result of razor-thin margins and quick turnarounds. Competing on quality against free labor is quite hard.
An HTML5 app turned native in 10 minutes with PhoneGap Build?
Sometimes people just need a bit of a kick up the arse to see the light.
I understand where he's coming from but he comes off as very aggressive. He could have made it passive aggressive though... Did he have to sign over his IP rights before working on it? He could have worked on it and got a feel for things. If he liked the code and company and salary negotiations no harm done. If not, and he wishes to be passive aggressive argue that they owe him money for IP or he'll sue for copy right infringement. Company's that do this walk a fine legal line. I like to see and understand a companies risk assessment, mitigation, and contigency planning...
This would be a phone that I'd actually be willing to move back to Android for. If the e-ink display API would be designed no worse than Android's main API, I'd hack all kinds of homegrown apps for it.
The way Clojure mitigates this is by having a REPL. Whenever I work on any code I can always run it immediately in the context of the application.

Let's say I'm refactoring a function, I can run it to see what it actually does and I can write a new function and test it immediately on the spot to make sure it has the same behavior.

When you're working in a REPL you always have confidence that whatever change you made does what you want immediately. There's no recompile cycle, you don't have to restart your application and build up the state to see what effect the change has.

This allows you to refactor things and be very confident that you're not breaking anything. Coupled with high level integration tests you can be confident that all the use cases work correctly without having to have a ton of unit tests.

Having worked with Clojure it really shocks me that most modern languages do not have any REPL integrating in the editor and you still have the code/compile/run cycles.
I don't see any Java examples on that page, just Clojure.
espcially if your talking about moving things around a factory or store. I'm suprised forklifts aren't autmated already. they don't move fast I wouldn't think next gen kinect would be sufficent to detect obsticals find pallets. if you need something to go upstairs hand it off to something with flippers or legs. Also, I could see something like the assitant in Ironman with one arm and mobile being useful. Maybe some with suction cups as end.
you charge $56/hr in a daily rate? O_o
Can you be more specific? What minor crimes are you talking about? What's the breakdown of crimes for the the current prison population? Have any references to articles that have a deeper discussion so we can come up to speed?
It's not about revenge.

Our motivation to not do things is driven by consequences.

When the balance of power exists so that those who determine consequences for people can do so out of self-interest, they need to be held up to the same standards and face equal consequences themselves.

The prosecutor should have a sentence passed against him to ensure others do not follow suit with "$500 and 500 hours community service, oh and I can still be a legal consultant for a corporation - I can accept that risk for some gain"...
Too bad! Interviewees are not guinea pigs! High time that interviewers realize this.
It’s the same content, why would you need two interfaces, just because your consumers speak different languages?

Because you then can change one without affecting the other. If your html is parsed automatically, the parsing can break when you update your html to fix a design flaw.

OP has some good points though, those APIs look retarded.

Content negotiation could be nice, but it doesn't remove the need for keys in most cases, and adding this to your stack could be harder than just making a simple API.

Ask for new representations on your existing URLs.
Only by embracing the information-oriented nature of the Web, we can provide sustainable access to our information for years to come

Yes. But won't the answer, in most cases, be a simple "API"? (not a real API, in the programming sense)
Yup, doing a big of handwavy math also demonstrates this: You are comparing something like x^N - x^M with 2^x - x^M. The second will always grow big rapidly, while the first could stay small, but it can also grow arbitrarily large. In fact, it is bound to do so for N > M and it will do so quite rapidly if N >> M.
:) Well, it's open source, so you can check what it does and even run it locally without internet connection if you really want.

Good idea though, I'll have to add form for credit card details :)
Because it will be a huge mess once you hit your first merge conflict or want to use proper branches. SVN is usable for source code management, but not really for efficient collaboration.

edit: And if the SVN server goes down / messed up by someone, you're essentially forced to sit around and staring into the sky. With git, all you may have to do is fiddle a bit with merging if someone did a git push --force. And if the server is down, you still are able to work on your own.
> He's trying to protect his business from a hostile actor - Microsoft.

And Microsoft are just responding to Android and iOS app stores.
Well, I've made a interview at a company that asked for pair programming in their codebase, but actually paid for it. Since it was just 2 hours, it was cheap for them, and I didn't felt exploited. I felt it was a great way to get to know the company and discuss real code.
I really don't like algorithmic interviews, they normally just test you CS 101 memory under pressure.
Yup. That's why requests aren't function calls. REST is a different architecture than RPC, which is why you need all of these conventions to do RPC over HTTP: you're mapping one architecture onto another.
Android developer and want to work in Stockholm, Sweden?
Want to develop apps that got several 100 000 users?
If you need an apartment when moving here, we fix that.
Work experience 2-3 years and a great track record. Send me a e-mail to mikael.ytterstrom@screeninteraction.com and check out www.screeninteraction.com
You are certain, after reading some newspaper articles, that Ken Anderson abused his position for personal gain, and the most important thing to you is that he be punished more severely. Your slogan: "an eye for an eye".

Other people were certain, after reading some newspaper articles, that Michael Morton murdered his wife because she would not submit to him sexually, and the most important thing to them was that he be punished more severely. Their slogan: "an eye for an eye".

See the similarity now?
Thats a really inefficient way of encoding it.

It would result in a much smaller scriptPubKey to encode something like this instead:

S_pub OP_CHECKSIG OP_SWAP B_pub OP_CHECKSIG OP_ADD OP_DUP OP_DUP OP_VERIFY OP_2 OP_EQUAL OP_NOTIF 0 2 A1_pub A2_pub A3_pub 3 OP_CHECKMULTISIGVERIFY OP_ENDIF

Or something like that— only the 5 pubkeys involved instead of adding extra ones.
very sad story. I still can't believe the prosecuter only served 5 days in jail and paid a minor fine. These injustices are crushing my heart. I do really want to believe in fairness and Justice but after reading such a piece I cannot maintain those illusions.

What can we do as individuals and as a society to improve the Justice system and help rehabilitate former criminals? This is an area where we should also have start-ups looking to make a better tomorrow. Isn't that also part of "Changing The World"?