skysight-inc/HackerNews huggingface dataset:
"Wrong" sounds too strong as many startups proceed this way and some people (like Seth Godin yesterday) more or less suggest this approach. However I'm strongly convinced that verifying problem before solution can bring extra value and inspiration for relatively small effort. If I was you I'd proceed in that order: 1. Talk to at least 10-20 friends&acquaintances about their experiences with job interviews: What's the most difficult (stressing etc.) thing for them? How exactly do they prepare? How much time does it take? What specific information, advice, tips are they looking for? Where do they search? How often do they find it? How helpful these tips are? How strong is their desire to prepare better? And similar questions to deeply understand what is the problem, how they are trying to solve it and how satisfied they are with the current solution. This info will provide you qualitative data that will help you build better survey for online problem verification. These interviews will also probably suggest you online sources for survey respondents (specific forums, communities, Q&A sites etc.) where people searching for such solution are gathering. I guess Quora and LinkedIn might be such places. At this moment the survey will work for you amassing the quantitative data about the problem assumptions. And even more - interviews will help you identify specific keywords related to your service which might be used to gain traffic for the survey and later for the product itself. When you have this you can finally test the solution itself and I guess it'll be better than the initial idea. As a summary: definitely you need to define and understand you target group (who are they? how do they think and feel? what are the best channels to communicate with them? etc.) to bring them solution they need and present it in a way that will be attractive for them. In addition to obligatory ;) stuff by by Eric Ries (Lean Startup) and Steve Blank (Customer Development) you may find "This service design thinking" book inspiring. And in case you would need some specific feedback about your project feel free to contact me via Google+. I'll be happy to help because recruitment field is in my scope of interested. And I've experienced my share of unprepared candidates already :)
Where I used to play, we mostly played standard chess openings. Bughouse is different enough that one can have expert chess players playing against novices and since it is team-vs-team, the novice doesn't get totally stomped flat.

Something rather common was for most of the pieces to end up on one board, so my guess is that these strange openings are intended to block off places you'd normally use to drop in a piece that your team-mate captured. So it becomes more like Go,
Awesome. I had just made a comment asking for this. :)
Along that same lines... you never see a good ninja. So if I'm hired under the guise of being a ninja you can expect to never see me in the office. So telecommuting would be expected?
Actually, that article concludes against equal proportions:

HBR: But gender does play a role?

Malone: It's a preliminary finding--and not a conventional one. The standard argument is that diversity is good and you should have both men and women in a group. But so far, the data show, the more women, the better.

Woolley: We have early evidence that performance may flatten out at the extreme end--that there should be a little gender diversity rather than all women.
Does anyone has some info on the architecture required to maintain a service like this? Servers, db, etc?
Excellent point - and different from the original poster - and I feel silly for forgetting about it. Google knows your interests and who you are...and what you'd buy.

Would be nice if Facebook would offer Adsense.
Job descriptions just shouldn't have "rock star" or "ninja" unless they are hired on their ability to perform music in front of an audience or on their katana wielding skills.
My cousin, for instance, uses her Mac as a word processor, email reader, Wikipedia reader or DVD player 90% of the time. Works in TextEdit, doesn't download basically anything at all. Does everything basically inside Apple's walled garden. The only "dangerous" thing she did in the past is using MSN for Windows. This could mean automatically receiving payloads and run them by just having an infected contact, because of Microsoft's "wise" defaults. This doesn't happen on Adium. I think she doesn't login to that network much anymore, now it's all about Jabber (gtalk) and Skype I reckon.

Unless Apple started injecting payloads there's basically no plausible way to get her infected. She doesn't even "browse the net" for the most part, doesn't click on links, doesn't give a f.

There are safe habits. AV companies would like to have you thinking you're always about to have your nix based system rooted, but this is damn unlikely for most people not using dodgy sites. I fancy my chances to get struck by lightning above her chances of having her system compromised, and I don't get out of my house scared.
1st Rule of DevOps – You Do Not Talk About DevOps
The more useful data is that any ad that uses such language doesn't actually employ any ninjas or rockstars.

At best it has an HR person who never managed to stop being 17years old, typically it's a bunch of trend following losers, at worst it's a bunch of creeps who think they can under-pay and over-work you in return for having a pinball table in the corner.
Bughouse lets you have experts and novices playing without the novices getting totally stomped. Because you can always move a piece, or place a piece that your team-mate captured, you have a lot more options. This also makes it far more fun for lesser skilled players than regular chess.
The content appears to be pay-walled.

I haven't read the article.

Please be careful when controlling food (your body, your choice etc) because eating disorders are not fun and it's possible (although unlikely) to develop an ED through over rigorous food control.
The main problem here is that Google has god awful customers service. Even for their paying customer on Google Apps. Just terrible.
if you don't mind, I'm going to borrow that line from you...
I think it's interesting how you assume you know what a woman thinks coming from a man. Have you asked women you know about their opinions about a Computer Science degree?
Basically this... And so many old school peddlers have stuck with ICQ and it's just easier for them to keep using it instead of adopting a new modern form of instant messaging.
Because the continuous integration runs tests for all components at HEAD, not at every random possible combination that could end up on a machine. The key to releases is repeatability and consistency. Copying one big blob to every machine is repeatable and consistent. Installing a bunch of libraries and updating things piecemeal is much more difficult to do right. Internal bandwidth is cheap, so this is almost a no-brainer. Even without an internal bittorrent distribution mechanism, it's still easy.

The reason why people tend to gravitate to incremental deployments for web applications is because the typical tools encourage it; modules get installed in separate directories, each part of the app is a separate file (back in the CGI days), etc. When you compile everything into one file, though, then you just copy that file around to deploy. It's easier. (Ask a PHP programmer how to change one file, and it will probably be "change that one file". Ask a Java programmer, and it will be "fix the file, build a WAR, and replace the WAR". Tools dictate process, and the "scripting language" default is to work on a file level instead of an application level.)

I've always wanted one-file deployment for my personal applications, but I never saw anyone doing it so I assumed I was wrong. But nope, it turns out that everyone else was wrong :)
They actually don't provide a justification. That blog makes the argument that omitting them is harmless. Neither GitHub nor the blog make an argument for why you should omit them, however.
To add to what others have said most Facebook hires learn PHP during the boot camp process. The continued use of the PHP is definitely not due to lack of experience with other languages or some misplaced fondness for the language.

When you work on a codebase the size of Facebook's the core language becomes less important than the abstractions and framework that have been built around it. As well as having sane internal libraries Facebook have added extensions to the language like XHP and the yield keyword (http://www.serversidemagazine.com/news/10-questions-with-fac...) which make it much nicer to use.
My opinion is that "female-friendly fields" is (or should be) "software engineering". Thus "lets see them set up a special fund or something for female-friendly fields" reduces to the current state of the program.
Their style guide disagrees with mine! KILL THEM ALL!!!

Did you read the article they linked to? I did. I still disagree with the style rule, but I don't feel like I'd win an argument with them about it.
As an ex-googler, that was the funniest thing I've read all week...
I made Cactus as a simple Jekyll Python/Django alternative. Using it for a blog is fairly easy, but I didn't get around to making an example for it yet: https://github.com/koenbok/Cactus
I totally agree.

If I understood your comment, basically, "treating candidates with respect - especially inexperienced/unconventional candidates - allows hiring if you already know how to find great candidates"

I've seen a ton of benefits to treating candidates _and_ employees well.

• Many employees will prefer to stay in a job where they are treated well (despite taking a hit in lifestyle / pay) [1]

• Establishing a "social contract" with your employees provides some protection against managers who might drive away high-value candidates / employees

• During tough pivots (the current economic climate tends to produce this), a core of effective employees can execute while mediocre employees will flounder

[1] http://freem.vmth.ucdavis.edu/~saintly/bio/portrait.html
Like everyone who's ever been caught doing something bad, they learned an important lesson: don't get caught.
Show HN: Visualization Mapping FDA Approved Drugs to Diseases
Mojito doesn't try to be "write-once run-anywhere." It doesn't provide any UI or device abstraction layers by itself, beyond what YUI has always done.

It's an MVC app framework, oriented towards composing modules/widgets-- aka mojits. If you want to render your stuff server-side, you can. If you change your mind, it's a pretty trivial change-- and in fact you could do it at runtime (Yahoo has a search product in beta that does this after instrumenting the connection/device speeds).

There will always be server-side only stuff, but at least you don't need to switch languages or frameworks when you decide what to do where.

A sweet spot might be an online/offline HTML5 app that uses YQL or other webservices, for which you want to provide desktop, tablet, and smartphone versions and/or native versions via phonegap or similar.

That said it's definitely not for everyone, and it's still a very young project.

(disclaimer: I work at Yahoo)
Twitter releases Common Locale Data Repository gem
Yes, but that's not the point. The point is this comment while seeming innocent is an absurd rationalization for the behavior linked to in this post.
I don't think that is true. As for as I recall, the World3 model includes price feedbacks like this.

But even if it didn't, one of the lessons of World3 is that it takes time for negative feedbacks like this to achieve equilibrium. If the feedback is slow enough, you get overshoots, and those overshoots either are (by definition) or could trigger (as a side effect) environmentally and socially damaging events. In the case of population, for example, the recovery after a large overshoot could take the form of mass famine or civil war.

There is another problem with the argument that many free market optimists make about energy: to actually scale up whatever fancy clean-energy technology happens to become economically viable in the future might require huge swathes of our economies to be reconfigured at an impractical rate.

To give an example, there are physical limits to how quickly you can ramp up the volume of solar panels, no matter how cheap the technology is, to do with quickly we can ramp up the production of pure silicon, build plants that make solar panels, and train engineers to oversee those plants and install those panels into the grid.

Of course, we can't quantify these limits for some mystery future technology, but we can play the game for known technologies, and it doesn't look good.

In particular, it seems that it is only really realistic to be off fossil fuels by 2050 if we start transitioning aggressively now using many different approaches --simultaneously. In other words, we need to place a lot of large bets, not just one large bet or several small ones -- see [1] for example.

Given the reluctance of the world's largest producers, consumers, and polluters to even get serious about one of these approaches, it seems pretty hopeless that we have the political will to execute on all of them, simultaneously, at global scale, as we need to.

As usual, the poor will suffer disproportionately.

[1] http://www.aaas.org/news/press_room/climate_change/mtg_20070...
Page 15 of the complaint is fairly damming. Apparently "Campbells Biology" uses a bear eating a fish + running to explain thermodynamics and even this example appears in their version...
It might possibly be legal, but I feel it shouldn't be.
Tax IDs and SSN numbers are.
I think New Relic saves us money - the amount of optimizations we've done because of them is just crazy and by now would have saved us a couple servers and hardware upgrades at least.

Their sales dudes like startups, we were only lightly funded when we started using them - garth@newrelic could probably help you.
The future of MacRuby
5-star Feedback Systems are Broken
The Joker
I'm a semi-introvert graduating with my BS in CS and am looking for jobs right now.

And this is all I ever feel. I read dozens of job ads across the country (I look through all of them because I really want to get out and move some place new, see the world - being fresh out of college is the best time for me to do that and all) and in the process I see only two kinds of jobs for someone like me.

The ads either come across as wanting rock star geniuses that could develop in a month the entirety of the next facebook or google in their sleep, or they come off as grossly incompentant in that they don't know what they want from an employee.

When an ad lists skill sets from assembly to rails to genetic algorithms I just sigh because the company obviously doesn't know what they want, and I want to work some where that I can not only get better at my trade and create great things but also have confidence in the business not going under in a few months.

Simultaneously, the other set of job seekers want 5+ years experience for a startup and they use the rock star vocabulary, and I get turned off on that because I am not the second coming of John Carmack or Bill Gates, I wish I was, but I just am not that smart.

Compound that with the reality that I have a passion for software and as a result I only want to work on things I find interesting and useful myself (eating my own dog food) and I might consider one ad in a hundred. And I'm not even location limited!

It just seems to me like there is no middle ground, either you are a genius rock star or the employer appears clueless about what they are after in a developer. It really grinds my gears with all this job hunting shenanigans.
Votizen, Politix, Politify aim to harness the political Web in 2012
Yeah you're right. There's no solid reason to do so, in the face of a solid reason not to.
Take them to a small claims court for damages (money, plus wasted hours dealing with it at your hourly rate). They will probably send some clueless legal intern without any proof.
If bandwidth were metered and people paid per byte, I think the amount of sharing would drop. People share their bandwidth because they are paying for downstream and they also happen to get a chunk of upstream bandwidth with that.

Regarding storage, they need to store the item locally to consume it. There are probably very few individuals that store all the torrents they've ever downloaded in perpetuity and remain as seeders of those.

But yes, I agree that regardless of the causing circumstances, the fact that people are all making copies of things and sharing them is remarkable. I think it is analogue to what a lot of people want to see with 3D printing.

Replace "bandwidth and storage" with "the transportation of raw materials," and torrent software with 3D printing, and you've got yourself an interesting sea change in the manufacturing industry. I wonder if they will lobby with the same intensity that the RIAA and MPAA have.
created: 263 days ago

you should really know better than this
In some situations, not following the behavior of the crowd has an effect. I've been at parties where people were passing round a bong or whatever and declined and it definitely separates you from the group for better or worse.

I'm old and stubborn enough now to know that if I don't want to do something, being outside of the crowd is no big deal. But it's still something that occurs, and some people are particularly sensitive to the effects of going against the flow or find it very difficult to do that.
three gold nuggets
Robotic support brings freedom to paraplegics
A Rubyist’s Impressions of Common Lisp
You have a very narrow understanding of what internet is. It hurts Google, in an indirect, but very deep way:
Google should be most interested in the proliferation and diversity of independent sites, since this is what they search. They should be especially interested in the long-tail. When they cut revenue sources for them, the eyeballs go to places that they cannot touch/financially hurt or more importantly they cannot search, i.e. to Facebook.
Has anyone heard of the Reddit API
I just stumbled upon this but unfortunately I'm unable to find good documentation...
I meant conversation less in a marketing sense, and more in a crowdsourcing sense. To see what ideas people come up with, what they would like to use it for, and so on.

Sure there is the famous "don't ask users what they want", but Google might not even be asking users what they want, they might be asking engineers and scientists. They might be in it because they want to create a cool product, not because they want to appease the highest possible amount of people.
the only tools that will break your code if you don't use semicolons are so old they shouldn't be used for other reasons. At this point, you should really be using either yui compressor, closure compiler, or uglifyjs for reasons that have nothing to do automatic semi-colon insertion or not.

If you are still using something like packer, that bit of advice will take about 5 minutes of work, and give you significant decreasing of file size.

Semi-colons need to be in 1 place, the beginning of a line that starts with a (, since that is the one place that automatic semicolon insertion will really screw you. If it makes you feel good to write a semi colon at the end of every line I don't think anyone is stopping you, but it isn't the language or tools that require it. You can also feel free to explicitly wrap every statement in parens (because it is necessary in a few cases), or end each line with a // after your semi-colon, all these are freedoms the language gives you, but are as necessary as semi-colons.

I haven't been using unnecessary semi-colons in js for years, and have yet to run into a problem.
Full Show 4/4/12: SCOTUS V. CONSTITUTION
[PHP] PSR-0: Great Idea, Bastardised Execution
walk around wearing t-shirts with something clever about your product...
It will generally work for static files served up by the major web servers. Other than that: no.
Look at me outwitting these fictionalized characters I've created

vs.

Here are some interesting ideas I have.
Ah-ha, yes there is. Sorry.
Rock Star: that guy who shows up late and worked on a hit project 15 years ago that he's always bringing up.

Ninja: that guy who's never at his desk and never says anything in meetings.
Locksmith Phoenix
Locksmith Phoenix: Power Locksmith Provide 24 Hr Emergency Locksmith Service in Phoenix AZ, Seattle WA and Scottsdale. We Provide Complete Residential, Commercial and and Automotive Locksmith Services. CALL 877-562-5322 Toll Free.
I think this is an important point in analyzing advertising.

The core of advertising is generally not to match a user to a product that fits them well and will be genuinely a good use of time/money. The end goal of most advertisements is to sell a product, or to change the way you view a company, regardless of how closely the company and the products matches your needs and ideals.

Many of the most successful forms of advertising use a certain level of behavior modification via methods like classical conditioning. Instead of showing a fancy car, they show a fancy car and a very attractive woman, and you are more likely to associate 'want' with the car as a result of the woman. Food companies will often try to advertise to you at times and locations where you are most likely to be hungry, so that when you are hungry again, you are more likely to think about their food.

I would view many of these types of advertising as parasitic, because they allow potentially inferior companies and products to out-compete potentially superior companies and products.

I do not think that most people consider this consciously, but perhaps it plays into their subconscious processing of advertisements. They click on a cool looking advertisement, and find a less cool product (or maybe a product that they recognize as overpriced), and then they associate that form of advertising (banner, etc.) with a gimmick, and therefore are less likely to follow through on that advertisement format in the future.

To summarize, I think that the 'shitty clickthrough rate' effect would be much less significant if advertisements were less gimmicky and more authentic, and geared towards matching the customer to the product that matches them, instead of matching the product to a potential customer.
What exactly is a ninja or a rockstar in terms of programming? If you're not a rockstar what are you? Would anyone ever actually describe themselves as a rockstar programmer?

I was pretty glad to see "anyone who uses rockstar as an adjective" on the list of people take out in the God Bless America trailer.
With HTTP, your application IS your API
A former colleague handles IP matters like this. She's a startup lawyer, so her rates are generally competitive in the price range you're thinking of.

Here's her contact info if you are interested:
(323) 929-7185
linda@cambrianlaw.com
Having spent more than a year "convincing the local papers" how they could expand into local digital, and mostly having very smart people nod sagely then do nothing, Google has little to fear from them IMO.