skysight-inc/HackerNews huggingface dataset:
Didn't read the article but I'm going to go right ahead and assume it's just a part of the website hosted on a third party server. MS does the same thing (they have some vendors that handle their site traffic that run linux boxes)
As a start-up CEO in the hiring-efficiency space, I get to see a lot of company's hiring process in gory detail. Anyone who's been around new start-ups (and old guys, see: Google) has seen a great candidate withdraw from a req due to long response time. In a larger organization these inefficiencies can be handled by adding more schedulers, sourcers, recruiters, but in a small start-up you need a top-down commitment to speedy processing of candidates.

As a company gets larger (~series A) there comes a sudden crunch wherein you need 10 developers, yesterday. At that moment, if you haven't laid down the ground work for a successful recruiting/hiring strategy you can experience a very lossy hiring process. You'll miss out on great opportunities to companies who have spent the time, money and effort to make their process efficient.

To the articles recommendations, I would add the following:

- For top tier talent, recruiting is more like sales: you need to sell your company to the recruit, not vice versa.

- For each requisition do the following: decide what the relevant skills/requirements for the position, decide who on the interview team will assess each of those skills, train your interviewers to spend 1/2 their time selling the company and why they love working there and 1/2 their time grilling the applicant on their focus area. This forces you to think critically about what you're looking for (forces understanding of the org chart) and gives each person agency in the process (I'm in charge of sussing out algorithmic ability).

- Corollary to the above: train your interviewers. Make sure they know what they're looking for both culturally and technically, and make sure they have the ability to assess those properties (or lack thereof). Interviewers are your company's brand emissaries (and the source of many candidates) if they can't communicate well the recruits will come away with a bad experience.

- Track things: I think of recruiting like sales. If a VC asked you how your sales was going you wouldn't say something like "OK", you'd have numbers, metrics, graphs, funnels, pipelines, etc etc. Though this can feel a bit overkill in the beginning, getting in the habit of monitoring your candidate pipeline is extremely important as you scale. Small inefficiencies become enshrined as 'best practice' and as you scale they can turn into huge holes for your organization. This is exactly the type of problem we're trying to mitigate/measure by bringing the traditional applicant tracking system into the inbox at www.foundryhiring.com.
Per-thread caching in libumem
Super Efficient, Super Tiny "Pico Projectors"
> Gosh I feel snarky today :)!

No, your post is pretty on point. I think everyone here feels this way to an extent.

Don't be sated by your dreams; reality feels better.
In my particular slice of the industry, it's because there's already thousands of developers out there supporting, extending, and maintaining the wheel that's already been invented.
Nobody force you to register with GoDaddy, and knowing this facts, you shouldn't.

But this still does not change the fact that IF GD gives the biggest $ for referrals, then that make sense for OP to integrate it, especially since he is not charging anything for this service and he made it on his spare time -- so I don't see the problem with this.
I always thought that limiting by the "size" of the database in megabytes was unintuitive with the 5MB/25MB plans (how many bytes are in a row?)- pricing per-row is much more developer friendly.

I wonder how they'll handle someone doing something awful like storing images or blobs in the database, though.
I'm not trying to be difficult here, just genuinely curious: why disable the arrow keys? Is it simply the speed boost you get from using hjkl on the home row vs moving your hand to the arrows?

I use Colemak, so hjkl is very counter-intuitive for me, whereas the arrow keys make sense and aren't /that/ far away.

EDIT: http://news.ycombinator.com/item?id=3684515 has some good explanations. So does anyone have suggestions for non-QWERTY users? remap the keys that are in the HJKL space, leading to a cascade of keys moved around? Deal with the counter-intuitiveness of actually using HJKL?
Vooza is the mobile web app you never knew you wanted
That works when you know what you want, i.e. for the first handful of apps. And on almost every tablet I've seen, games outnumber apps.

And when this thread got me curious and I was googling for Android versions of games I like, I had to dig through pages of spam to realize there was no port.
Samsung widens lead over Apple
How a Self-Taught 12-Year-Old Turned Spartz Media Into a Viral Media Titan
I find IMDB's "People who liked this also liked..." recommendation feature to work fairly well. You can hop from movie to movie until you find one that looks interesting.

http://www.imdb.com/title/tt0113277/

It's not a personalization system, but it probably works better than most of those in my experience.
Jeez. They didn't only get HuffPo'd; they got inception'd, too.
If your editor limits the max it impacts the average. If the days when coding dominates were more productive you could have fewer of them and spend more time designing, testing, writing documentation.
I'm not really familiar with how in-app purchases work, but it sounds like they result in some kind of receipt on the phone that the app can then check to know that you've made the purchase and so can enable the appropriate content or feature.

If that's the case, then once Apple fixes the protocol to block further exploits, would they be able to push something to the phone via an update that would check all the receipts on the phone against those that Apple records as having been legitimately purchased, and either disable the illegitimate ones, or even better charge for them?
I like that. I think that's part of the appeal here. I don't mean the electrodes in your brain part, but that there is no friction between your volition and something happening on the screen.
(Static) polymorphism is the very thing behind the STL. In order to decouple algorithms from data structures, you need a standard interface between them. In the case of the STL, that interface is iterators; other interfaces (such as stacks or ranges) are also possible, and in my experience much nicer to work with. But none of it requires OOP.
Anyone participating in these types of discussions should start with a disclaimer whether they are talking about static typing, where types are largely equated with classes (aka "class-based" programming), or message passing, where types are largely orthogonal to classes.

The latter concept is what Alan Kay had in mind when he "invented" OO although arguably C++ and Java have really popularized OO as class-based programming.
Oddly enough -- that was also Microsoft's self-image for many, many years.

The were the maverick to IBM's stodgy conformist.

Not that I saw them that way.
Stephen Covey wrote a profoundly influential book which made a big impact on my life. At a time when most self-help authors were focused on improving your personality, Covey was concerned about your character.

A quick summary of the habits:

1) Be Proactive - accept that while you can't control what happens to you, you can always control how you respond

2) Begin with the End in Mind - imagine what you'd like people to say about you at your funeral, live each day with that vision of your best self in mind

3) First things First - don't let the urgent take precedence over the important - make sure you devot time/energy to your highest priorities

4) Understand before Seeking to Be Understood - make sure you really listen to others, reflect what you hear, before trying to tell them anything

5) Think Win-Win - life works better when you don't see things as a battle, but as an opportunity to allow both/all parties to succeed

6) Synergy - ok, this was a little vague, but basically by working together you can achieve more

7) Sharpen the Saw - make sure to take time to renew yourself - exercise, sleep, recharge, learn new things, and keep yourself operating at the highest levels.

RIP Stephen. Tremendous respect for what you've embodied.
The CEO of LilyKade claims 30M installs, though that information may be outdated: http://www.linkedin.com/pub/dru-mundorff/16/556/560
People are doing this because it just works. With email nobody needs to be on the same page in terms of email software stack, TODO organization, having all tools necessary to file an item in TODO list on hand, etc. It's the same thing like using plain old paper to scribble down things and do something better later on, going over notes, when time/place permits.

It may look inefficient, but it doesn't have to be 100% efficient - people are inefficient, live with it.
Why HTML5 Will Succeed for Gaming
I know its hip to declare oneself a misfit and throw away the shackles of traditional academia, but what's the point of this post?

Being your 'weird self' means, by definition, that you have to be a misfit? Doesn't this imply than anyone who enjoyed or benefited from high school/college isn't being genuine? Am I missing something, or is this a puff piece for being offbeat?
Ditto here. Of all the habits, #5 is the one that stood out and intensely/profoundly changed my outlook on relationships.

It's funny how it seems obvious when you read it, but sometimes we need someone else to summarize and restate the obvious to look at it clearly and objectively.

Covey's anecdotes seal the deal: instead of vague platitudes he gives specific (if idealized) examples. Definitely unscientific, but certainly helps understand.
There's also the question how how that 100-200 LoC number is measured. They're looking at code that actually got checked in to the project they're looking at. I write less than that at work, but there's also an iceberg of code that wouldn't ever get counted. Iterating on multiple revisions before checking one in. Throwaway experiments. Side projects (the only reason I have them is that with fewer constraints they let me stretch my legs and code up a storm).
I'd be the first to tell you that I don't understand crypto. Most people don't.

You're unwilling to have this conversation again; I understand. Do you have a link to one of your talks? I'd be interested in watching.

Can you at least tell me what definition you're using for "fall", if not key retrieval? Replay attack? Information leakage?

Edit:

> "I don't understand the vulnerabilities you're talking about so I'm going to assume there's something basic about how stuff works that I grasp but you do not"

Sorry if it came off that way! I'm assuming that you understand something basic about how this works that I do not, and wondering what it is :)
The candle/light bulb analogy is the wrong analogy. The correct one is the light socket/wall outlet analogy. When electricity was first run into homes, it was all about light. So houses would have screw in bulb sockets installed. As more useful electric devices became available, people screwed adapters into the light sockets to run their devices. What they really needed were wall outlets (the Edison plugs we have in the US today).

Wall outlets didn't kill the need for light sockets, they simply split off certain functionality that wasn't best served by those sockets, because those sockets were never designed for that purpose. Light bulbs killed the candle (except emergency, devotional, and mood lighting) and I don't thing todo, calendar, task management apps will kill email, but simply return it to it original, more limited purpose.
>Well if 95% of the population use a term to mean one thing, then arguing that no it really means something else doesn't get you anywhere.

It's not about getting "somewhere". It's called computer SCIENCE, remember?
http://reddit.com/r/netflix/
How? Because they have a large market share in certain product categories?

I see that kind of out of the box thinking and pure passion in many of their most recent designs. The iPhone is a perfect example. Look at where that paradigm shifting product has taken them, and think about how that device is only 5 years old. I see the same transformative execution and design in their iPad, and now the rest of the OEMs are desperately trying to catch up instead of having delivered. Intel had to invent a new product category just to first describe, and then compete with the Macbook Air.

When I try to imagine what that quote means for Apple, I always thought it meant designing the absolute best products for people, no matter what, -no compromises. That they have delivered beyond what anybody could have possibly expected is a realization of that quote, not a negation to me. But maybe you take it to mean something else? They've certainly changed the world...
I would say solving the right problem is the bottleneck. Who the fuck cares what editor you use? Generally, they all work. Startups don't fail because:

1) You can't search through code quickly enough.

2) You couldn't secure the next round of funding because no one was using Sublime Text, or TextMate, or IntelliJ, or Vim, or Emacs.

3) It didn't have all the fancy features that essentially boil down to developer masterbating.

Remember, all startups are supposed to solve a problem that is worth money. WE SERIOUSLY NEED TO STOP TALKING ABOUT EDITORS PEOPLE! Start ups fail because you are solving a problem that doesn't need to be solved, you can't find product-market fit, you have a shitty UI that no one can figure out, your applications are slow or have crazy down-time, or you fail to reach enough of your market to sustain a functioning business model, etc.

None of the problems are code. Code is a means to an end. I'd say code editors are sad not because they focus on the file instead of the class, module or function. I'd say code editors are sad because they focus on code in general that only exists because solving the real problem another way isn't possible.

Let's focus on solving the right problems. Problems that need to be solved, and not problems that look like other problems.

Can we all agree to stop posting text and code editor reviews and editorials and focus on becoming a more integrated component of a larger business? Just for one week, let's not talk about editors and instead think outside of our developer box.

Sorry for the rant but this sort of discussion is not productive, produces flame wars, pedantic quibbling and we never end up anywhere else than where we started. Code editors are like butt-holes, everyone has one and they all stink for one reason or another. Let's not forget that they exist to put poop in the toilet.

*Edit: Some have made extremely valid points that its not all about business, start-ups or money. I agree. My more broader statement is this: the editor one uses is largely a matter of preference and is not the determining factor of success for any project, professional or otherwise. Being able to solve the task at hand (whatever it may be) is largely a function of the focus, determination, experience, and skill of the person using it. At the end of the day which editor you use shouldn't make a damn bit of a difference of the actual bits you compile.
Scheduled for 'September', according to a Facebook post by Asus Italia that everyone is referring to:

https://www.facebook.com/ASUS.Italia/posts/180844915379890

I hadn't heard about that, and it still seems like a half-assed international release to me :(
From PR disaster to PR disaster. Good job, Apple. Did you really think that no one will dispute this and make a big deal about it online? In today's highly-connected and online world, honesty pays. Because if there's anything wrong or dishonest, someone, somewhere, will find out about it, and then let the whole world know.
I agree. When I use vim, I just know the key to press to move around. I don't think "move to the next word -> w". I know I want to move the cursor and my fingers know where to be but not really what key I am pressing.
Neat.. kinda fun.

One thing is you might want to allow people to configure the META key. I have Emacs set up so that the Command key is META, so all my muscle memory is ruined when trying to run through the drills.

But I like the concept and might use it to increase my shortcut kung-fu.
That's really fun. I love the site design, very slick.

Found a "bug". Some of the keyboard shortcuts conflict with my browser shortcuts.

For example, in one of the emacs drills, to move down a line (ctrl + n) it causes chrome to open a new window... so I could never complete the drill because of this.
I was just responding to the fact that David Holz referred to existing touch apps as "legacy" apps. It does have a charge to it which is why I used it in the headline. What I would think all the hackers would like about the Leap is that it progressively enhances on top of existing touch (and GUI) UIs. It will replace those things to the extent that it's useful to people, but it doesn't seem like it breaks anything downstream of it.
It seems like high school & college girls would go bananas for this. They'd get to peruse clothes all day and try to make money? The right in on Facebook or Twitter seems like it would go a long ways.
The worst part is, they could have said that they had 7k developers who in turn have 100m users, and we'd still be impressed. Instead they just smeared egg all over their own faces.
I don't know about "rogue/maverick," but I'll take "good" in a world of companies still rehashing 20 year-old laptop designs.
Maccman, not a huge deal, but when you said "A different doctor might have put her on medication and told her to calm down." you're quoting Robinson.
I had pretty much exact problem. We keep index of row keys in Cassandra on time partitioned data (by hour), but do not want to re-insert the index each time there is a piece of data.

A ConcurrentLinkedHashMap (http://code.google.com/p/concurrentlinkedhashmap/) solved it easily. It does use more RAM though... but an insignificant amount on our heap.
Collisions not so rare for a small bucket.
The security of most block ciphers revolves, in some ways, on the difficulty of brute force iterating through very large numbers --- 2^128, say.

"Byte-at-a-time decryption" means creating a scenario where attackers can brute force numbers like 2^8, winning a single byte of "plaintext" (or whatever the equivalent is depending on the primitive you're targeting). If your block size is 16 bytes long, the attacker might have to brute force 2^8 16 times; with a laptop, you might be talking about whole seconds of work.

Block cipher attacks generally never recover crypto keys.

I am being intentionally vague. Not because I want to keep information from you, but because I don't want to create yet another crypto thread that gives developers a false sense of knowing what the risks are when building crypto.

If this is something you're seriously interested in, and you can code in any programming language, email me and I'll give you a syllabus of straightforward things to work on.
why do misfits have to do things or change the world? Just be a misfit for the sake of being a misfit. Just be yourself.

You're trying to fit misfits into the same type of homogenous box that school systems put kids in.
HN discussions are different from other communities. I don't mind threads that veer off-topic, religious or not.

http://www.paulgraham.com/disagree.html
It's what is more commonly called a "circlejerk" - where everyone gets to feel good/superior for a while but nothing is actually accomplished.
We've integrated with Facebook's Open Graph so we've got a pretty good idea of demographics, and high school/early college are the most active on the social side of the site so far.

Interestingly enough, it's pretty popular in Eatern Europe as well. Women in Poland love discovering fashion.
NASA’S Car-Sized Rover Nears Daring Landing on Mars
Talk is about 36 minutes (then questions). The theoretical part at the beginning is the best, and then seeing the actual implementation for Bloom was very informative. I do think this will highly influence my solutions for these kinds of problems, and this talk is hitting the nail on the head for the kinds of problems you have to deal with in eventually consistent systems.

Great stuff!
That's a very attractive price point. I'm really considering switching Tehula[1]'s backend. The previous "basic" plan was too pricey for our needs right now. But this new option makes using Heroku Postgres really attractive.

[1] http://tehula.com
> but what's the point of this post?

Self-applauding circlejerk, followed by tea service.
Clojure: writing tail recursive functions without using recur
Just to contrast, as somebody that's a novice-to-intermediate vim user, I really like this so far. The action verb model feels like it mirrors how I think when using vim, so at first blush, for me at least, it feels like a good fit.

I don't know enough about Emacs to compare there, though.
But it sounds like this is exactly like those kludges.

Instead of detecting which browser the user has and saying "best viewed in X" where X is some other browser, how about detecting which features you need, and then giving a clear error on which were missing? This is better in many ways, for example if the next update to a browser adds the missing features to it, then it will just work on your site.
Ghostery gets rid of that, plus a whole host of others.
Easy nitpick, what if one of the officers gets sick, gets injured, or just plain forgets and goes home?
There's a direct way to do this:

Command + first letter button title

will activate that option, with a few caveats - Command-C won't work as Cancel, but Command-. will.
Where did you get the count data?
A demonstration of cymatics--the study of visible sound--with salt
Why is Steam so buggy on OS X?
Hmmm... now they need to bridge explaining the current plans with the new ones. Perhaps in the dashboard they will report both the size of the DB and the number of rows occupied.
I was thinking like 3/4 to 1/2 inch tubes of solid plastic. So maybe heavy-duty bolt cutters would be a good idea to get them off.

The crux of the idea is that only way to get the cuffs off is to break the cuff with a specific brute force that requires a large unconcealable device. Even with the device, you still need time/space to use it (5-10 mins).

So pretend that we would need a large UV lamp and 5 mins to melt through.
There’s always more to consider than just $/referral. For example blinking, pop-up ads might be more lucrative in the short term, but in the long term could turn to be too annoying, and end up putting off some users. The choice of monetization opportunities says a lot about the character and priorities a company has.

Like I said, I don’t want to take sides and start a flame war here, but it’s a fact that dealing with GoDaddy is controversial, and no company operates in void — your choice of registrar or ad network has certain implications, that ought to be considered.
We've generally found that this sort abuse rarely happens. Generally developers utilize our services as they are intended. And it is much easier to release new services and watch for abuse than to pro-actively restrict them before-hand.

There is nothing wrong with storing blobs in the database - it is one of the data types. But a database is not a replacement for AWS S3 either.

If we did find someone abusively using the database - especially if it was affecting the overall quality of service - we would reach out to them directly to address it.
>I thought all of the OS X updates cost $19.99. Or am I wrong here?

You are wrong.