skysight-inc/HackerNews huggingface dataset:
The question is: what do you gain by categorizing them as self-identified black or white as opposed to not categorizing them at all or categorizing them, say, by the presence of some gene cluster or genetic marker associated with gout?

There is something to be gained, from a social or political angle. A public health advocate in government might say, "Hey, if we see this is a more common problem among a particular social community, maybe we can use the pre-existing channels of information distribution within that community to help them out."

But if your study were not approaching it from this public health angle, then what's the point of correlating gout with this other quasi-scientific socio-political factor? There may be other more suitable categorizations where this particular African-American/Caucasian distinction breaks down.
I'm building a new website, and I know that I definitely want to use Jenkins for CI.

However, with all the infrastructure stuff that's needed for a software organization, having all of these services hosted quickly becomes a nightmare to manage in itself?

By infrastructure stuff I mean all of the following and more (and the decision to run it yourself or have it hosted):
- Hosting - Amazon EC2 or Rackspace
- Bug and Task tracking - Bugzilla
- Version control - Git (Github private costs $/month)
- CI - Jenkins
- Deploy - Heroku (hosted) vs Capistrano scripts (DIY)

Because I like to do pretty much everything myself and save money whenever I can (I have been hosting several websites from my home desktop on dynamic DNS w/ freedns.afraid.org for years)--I am just about to finally give in and actually rent a VPS from Rackspace.

Knowing that all of these are services will always be needed (or at least, should be best practices) for collaborative software building, I would much rather build these out and customize them for myself for the years to come.

The only reason I'd switch over to hosted solutions is if I or someone on my team got too busy to maintain it in-house, and if the cost savings were justifiable in switching over.

After using Jenkins CI at my last company, I really enjoyed that experience, and absolutely must have it for all of my future projects. On my list of infrastructure stuff, CI comes after hosting and source control as a basic necessity, so it should on average cost the same or less than those.

I hope I'm not being so cheap and parsimonious as to offend you, but I'd like to see a version of your service offered in the $15 price range without much sacrifice in quality/service.
Add the OpenGL calls and your program will not be shorter than the Clojure program in any way that is interesting.
IANAL, but signing contracts in bad faith may under some circumstances be tortious. Your corporate liability shield probably does not protect you from tort claims.

You are shielded far more by your lack of meaningful assets. You aren't worth anything to sue. But there are clients, I promise you, who will turn out to be vindictive.

Incidentally, if you're 22 years old, you should still have an LLC.
The command line tool is much nicer than the GUI, but there is still no way to get easily machine parseable output. Unlike Git, all of the `tf` commands are porcelain. If you want plumbing, you need to code to the COM/C# APIs.
How recent was your experience with TFS? It's been around for 6 years and shipped 3 versions, that should be enough time for it to be good enough for dogfood.
Any attempt at imposing more than C-level abstraction onto a program like Tetris results in needlessly overcomplicated code that fails the 'simple and direct' test.
Can you provide a link for that dollar amount? At its peak in 1966, NASA was 4.4% of the federal budget. That's 5.9 billion dollars for that year. The population of the United States was 196 million at the time. This puts the cost of NASA at $30 (1966 dollars) per person. That's a lot a bang for the buck!

Source:
http://www.infoplease.com/year/1966.html
http://en.wikipedia.org/wiki/Budget_of_NASA
Same Thorium hype as usual.
"Just be lucky like I was" is rather poor advice.
Preparing for Emergency
I wouldn't sign a contract for personal liability on something that big, but bankruptcy law exists for a reason.
You use the word "friendliest" to describe a guy who three comments ago called someone a "douchebag" because his post was too long?

He's got a history of similar behavior. He really is a bit of a troll. He certainly doesn't follow HN guideline of "Don't say things you wouldn't say in a face to face conversation.".

My guess is PG only unbanned him so he wouldn't face the criticism of seeming to censor one of his critics.
When there's nothing to lose, there's everything to gain, but when there's everything to lose, there's alot more lawyering that will keep yer nose clean if something eventually goes south. Get a lawyer when there's really something to lose.
This is NOT NEW. The basic reaction chain has been well understood for decades. There are multiple issues to be solved with actually setting up a reactor to deliver power that the article doesn't even consider. Hype.
Nowadays a lot of companies try to add clauses that pierce the corporate veil (for example, having personal guarantees)
You have to balance your risk and reward and take the biggest risks when you have little to lose. The riskiest thing you can do is play it safe.
Oh, one more thing to add: Google Apps is free for up to 10 users, so arguably, email and collaboration is even more important than the other infrastructure stuff. Paying for a luxury when something even more basic is free? Hmmm...
> Then there was the time I wanted to hire my first full time employee. I was apprehensive to do it because I only had enough money to pay him for 2 months, unless I got another client fast.

> “Worry about that in 2 months,” Dad said.

Speaking from the perspective of that employee, fuck you.

OK, for the serious point: you may be not give a shit about risk. Good for you, you crazy risk taker! The world truly needs more people like you.

But for me? I've got a mortgage and a car payment and a wife who is trying to go through graduate school. I need to know that my ass isn't going to come into work on the 61st day and hear you say "Well, looks like we're outta cash -- sorry buddy..."

If, on the other hand, you share that risk with me up front, thanks -- you're a good boss.
Back in the day one of the reasons Uranium was picked was specifically because it resulted in weapon's grade by-products. You got energy + you could build nuclear stockpiles.

Also, I don't think this article does justice to just how far ahead India and China are in this field.

And all that isn't even accounting of the arcane crystals!
隆鼻好不好
The NYC MTA seems to have done an about-face from "you can't have any data, and we'll sue you if you do get it" [1] to opening up their data and holding app contests:

http://mtaappquest.com/

I'm still waiting on a real-time train schedule API, but they've come a long, long way.

[1] http://iplj.net/blog/archives/1346
Radbox.me: Instapaper for Video
Leave to Forbes to write a massively hyped headline, and then deliver NO useful information whatsoever on the topic at hand. I feel like I knew more about thorium's potential BEFORE reading this.

Is it just me, or is Forbes doing this a lot lately?
And WikiLeaks is just troublemakers, etc.

You do know that there's no official membership list for Anonymous and anyone, even you, could be Anonymous. Right? So yeah, it's vastly unlikely that you'd agree with everyone using the name.

Why do point it out as if that implies nobody could be doing anything worthwhile?
To clarify though, I believe the success he's had is most certainly NOT luck but rather hard work and merit. My comment was referring just to that specific article.
I envy your understanding—I'm struggling to figure out what that line is supposed to do. Is he switching to a different branch, squashing all of its commits into one, and then merging that branch back into master?
Is there a good resource on the topic? I've read countless hype articles but nothing good on the issues that need to be solved for it to actually happen.
A quick follow up, from those same sites you can work out that NASA costs Americans about $55/yr per person today. Not bad, maybe others would like to buy a video game instead. I however enjoy the pretty pictures from around the solar system.
Did you read the very last line of his post? "I’m not sure what the lesson is here."

I don't see him giving advice to anybody. I see him recounting some rather... debatable decisions early in his career.
Google TechTalk about it:
http://www.youtube.com/watch?v=AZR0UKxNPh8
> Then there was the time I wanted to hire my first full time employee. I was apprehensive to do it because I only had enough money to pay him for 2 months, unless I got another client fast.

> “Worry about that in 2 months,” Dad said.

This seems really dishonest. Yeah, everybody knows that startups are risky, but if you can't afford to pay more than 2 months of salary, then don't hire a full-timer. Either find a co-founder or hire a contractor instead.
I'm being downvoted. Am I wrong? Please let me know rather than punishing me for reasons unknown.
I once rode a motorbike drunk, with a stranger sitting behind me. We didn't die. Lesson learnt: I got lucky.

I don't drive drunk any more :-)
I'd prefer that the carpenter build the strongest/lightest product, only worrying about looks where someone can see it and strength where it matters.

To me the value of solid wood throughout is durability. If a composite material was better why not use it?
It'd be nice to see some more face-centric auto-avatars like robohash, but in a variety of styles.

While they're pretty cool looking, the cartoon-y feel doesn't necessarily work with every site design.
Then I think my username choice was a mistake :(
Then don't be employee #1. Ever.

I get your point, but if those things are true, then that would not be the proper job for you to take, no matter how risk prone or risk averse the founder is.
It's so easy to incorporate it should always be done. I assume when someone starts working with that kind of money and has knowledgeable lawyers advising them that they'll be told to do that.
This is why I have a problem with a statement like "race and IQ is not a legitimate matter for scientific inquiry."

But both are social-political constructs. They are labels. What do you gain by correlating some feature of human behavior under examination with them? (I provide one answer in another comment: the effective distribution of useful information through existing social channels.)

Yes, racial labels refer to something real. But it's like correlating geological data with the state of California. California refers to something real. But as a scientist why would I want to correlate seismic activity with the state borders of California as opposed to, say, some fault-line that runs out into the Pacific or up into Oregon?
I don't see any such complications in the Clojure code. Your C code fails to demonstrate anything more "simple and direct".
Sounds like the opposite advice to: http://www.vimeo.com/22053820 (Fuck you, pay me).

Should have found a better lawyer.
Not many companies could afford to pay their entire payroll for a quarter, if sales were $0.00 for that quarter.
That delicious should be called "a Yahoo castoff" is so damned depressing.
It is all a very vague science to try to look back in time. Centuries is not that long ago, and one can try to assume that remote indigenous populations are still similar. Lets assume we are talking thousands if not tens of thousands of years ago. There are a lot of things that scientists can try to interpret from skeletal and other bone remains, only some of them that would be a direct link to cancer. This is a good overview of some of the science that goes on for that in a context that is relevant to the discussion at hand: http://wholehealthsource.blogspot.com/2009/03/paleopathology...

Personally I am convinced that cancer is just one of many degenerative health issues. If you follow that line of reasoning, than the frequency of degenerative issues in skeletal remains are likely related to the frequency of cancer and any other degenerative health issue. As one example, if you simply see caries (cavities) in the remains of the teeth, that would also mean cancer was more likely to occur. (very healthy indigenous cultures have almost no cavities). Obviously this is very loose logic, and certain groups are more likely to have certain issues that are more or less likely to show up in skeletal remains, but I believe the general principle is sound.
Most companies also have steady revenue streams.
Sorting in C++ vs. C
I wish someone would write an expert system that works like his dad. Something that had some validation of what was a worthwhile risk and what was a risk that even if you tried to mitigate the risk really would still be a risk. (For instance, even if you had enough work to presume you could employ that employee for more than 2 months, that's not a guarantee. What if the contract with a customer was for 12 months, but 2 months in, right after staffing up, they just cancelled it and said "fucking sue me"? Kinda hard for the small startup to sue... and if they did, and they won, that win would be years after they had to let the employees go.)

You can't mitigate all risk, and being able to ignore the ones that you can't' do anything about is an important skill.

This goes for technical risk as well. I try not to over-architect. I spend a lot of time trying to decide which things need to be handled now, and which things can just be added later.
Being employee #1 is the worst of both worlds. You get the risk of a startup and you most likely will get very little payout if the startup is successful.

Most of the people I know that were employee #1 got nothing.
unlike the vast majority of things, thorium deserves all the hype it gets.
The markup changes don't give any performance advantages, they just help to standardize things. They aren't essential to HTML5 being useful. LocalStorage is one of the big advantages. Canvas has some interesting uses, although still needs work to be competitive. Video and Audio tags could be useful in the future, if a consensus is ever reached about codecs.

Basically, you're asking the wrong question. Switching to HTML5 for markup changes is silly. The power of HTML5 isn't in semantic changes, it's in everything else.
Ask HN: Why are there so many new versions of Firefox recently?
I switched to chrome a while back but I noticed that 4 new versions will be released this year: http://en.wikipedia.org/wiki/Firefox#Version_6.0. Prior to that a new version came out every 2+ years.
You should still be honest with employees. They'll prove better in the long run if you are. Not a lot of stories where withholding the truth from your employees ends up being something that a boss feels great about...
Right, but, given the amount of incredibly useful products and discoveries that have come out of NASA's "inefficient, non-modular, non-reusable, difficult-to-test" architectures (see: http://www.independent.co.uk/news/science/50-years-50-giant-...), I think such a broad statement about the way NASA works deserves a little more qualification than a witty one-word answer, don't you?
You need to be able to figure out what's negotiable and what isn't.

I work for one of those massive organizations that everyone hates doing business with, but sort of has to. I've watched dozens of vendors spin their wheels for months over boilerplate stuff that nobody is empowered to change. They ultimately lose the deal over something that ultimately didn't matter.
Pretty much all employment is risky. It doesn't matter that you have a car payment and a wife going thru graduate school. Those are financial risks you took.

Your employment could end at any time. The company could be seized by the government as part of some investigation and shut down, the CEO could be hit by a bus, you could screw up in a big way and get fired. You could be hit by a brain aneurism and simply not be there to provide for your car payment and your wife's schooling.

Every employee is taking risk that their employment might end for any number of reasons.

This is one of the reasons that, when something like that happened to me, I said "That's it, my livelihood will never be in someone else's hands again" ... and have been self employed / doing my own startups since.
Well considering that there are about 12,000 projects hosted on Drupal.org and that it has it's own packaging system this is a pretty pointless example. I've never met anyone using apt to install PHP applications. Given the ways that apt usually installs a PHP app, I'm not really surprised either.
I had the same reaction. It seems like DNT is more notable for reducing interest and effort in actual solutions. However, the EFF (whose opinion on this I'd trust) appears to indicate DNT is complimentary with things like AdBlock and IE's TPL's:

https://www.eff.org/deeplinks/2011/03/tracking-protection-li...
I am glad we are agreed it would still be shorter. It would also by my standards be simpler and more direct. But I'm not out to convince you or anyone else of that. Make up your own minds.

You're defining the term "in any way that is interesting" according to your prejudices and I am defining it according to mine. Let's leave it at that.

Zach's program is a lot nicer than what was originally posted. But please take a look at my program and tell me where additional abstractions would noticeably improve semantic and syntactic clarity. I can't find anything. The only thing that suggests itself is the recurring 'for (vector *v = t.v; v < t.v + 4; v++)' idiom. It's annoying to write bare-handed for loops, but I don't lose sleep over it.
That's reassuring.

(putting in my two weeks notice tomorrow to be employee #1)
Did you read the article? All or nothing, that's basically how HDMI-cables work.
Incorporating without sufficient capital makes it almost trivial to "pierce the veil" of incorporation and go directly after the company's owners.
Yeah, but if you're recounting what has worked well for you in your career, you're giving advice - even if you qualify it at the last minute with a totally wishy washy ending like that.

Also, if you've followed Kaplan since his (awesome) "Fucked Company" website you'll know that the man is no babe in the woods. IMO he has too good a grasp on the nature and consequences of risk to be "not sure" what the lesson is here.
I think the point to "fucking sue me" is that you don't "fucking sue" someone over something trivial. So, if the dollar value of some provision in the contract is not worth the cost of a lawsuit, in a way, it is kinda immaterial to the agreement because it would cost more to collect.

So, I think the article is trying to hit the middle road you're advocating, though didn't make it as explicitly clear as it could have.
For all kinds of things, like leases and such were the company is too young to have any credit. But a personal guarantee on delivering a website on time would be a bit much.
On self versus other identification I would expect differences to exist, and that those differences would depend on society, culture and environment but within a pretty small range.

Here's another study on distinguishing ancestry by continent

An ancestry informative marker set for determining continental origin: validation
and extension using human genome diversity panels:

http://www.biomedcentral.com/1471-2156/10/39

It only uses 93 SNPs and is also reliable, except for distinguishing South Asians from West Eurasians.
The difference is that most of those things are risks you can't reasonably plan for. If you know that the start-up you're working for has x months of runway, then you can plan for looking for a new gig, ensure you have savings to carry you over, or decide to work elsewhere.

But you can't plan for it if the company's owner hides it from you. If you think you need to lie to your staff about the company's finances, then you're an untrustworthy prick.

And if you get lucky, no one will ever know. And if you don't get lucky, everyone will know that you can't be trusted, and that could affect your ability to get contracts and employees at your next venture.
I may be confused myself, but I think he's doing what's described in the first example here: http://learn.github.com/p/rebasing.html (checkout a feature branch, rebase master onto it, then go back to master and merge in the branch - it gives a more linear-looking history which many people prefer).

If I'm right the point of the tip is just to simplify this set of steps into a one-liner (which would help if you did this rebase and merge often).

In any case, I'm pretty sure that this is separate from squashing all the commits on the feature branch.
It's more a matter of everyone is doing exactly what you pointed out which makes it a convention. The HTML5 folks are concentrating more on standardizing what people already do instead of trying to tell everyone what to do.
Not sure why I was downvoted here?

I am mid-level front end coder (HTML/CSS & plug and play Jquery scripts) who hasn't used HTML5 yet (i do use CSS3 often to design sites & code).

I've only glanced over the mark up and wondered why I would use that over what I've been using past 2 years.

I know there are <video> and <audio> mark up tags that in some years will kill the need to use flash. What are the other advantages - the everything else?
He is on master and probably just pulled/fetched the latest revisions. He has some work on a local feature branch.

* The first command switches over to that feature branch.

* The second command rebases off of master, which basically rewinds the changes on his branch and applies them to the latest version from master - think of this like getting latest and merging in your pending changes.

* The third command switches back to master.

* The fourth command merges the feature branch into master - this should be what is called a "fast-forward merge" and not require a separate merge commit since you rebased your branch.

The rebase is really used to make it a cleaner merge back into master (and a cleaner history in general), not to squash commits in this case (though you also would use rebase to squash, that's another topic).

What I pointed out is that (for me at least) the rebase from master is not usually "clean" - meaning there are merge conflicts that I have to resolve - so chaining together shell commands like this doesn't really help when the second command is going to need intervention from me before I can run the third.

Hope that helps (and I hope my analysis is right or I'll look silly!)
Chrome releases a stable version each 6 weeks. So does Firefox now. But both of them have 2-3 other versions that are ahead of the stable one and go from dev to beta, or something like that. But those are not stable ones so you can disregard those. They also change every 6 weeks I believe.

So when Chrome 14 stable is out, Chrome 15 beta is out and also Chrome 16 Canary. Then in 6 more weeks, Chrome 15 stable will be out, Chrome 16 beta, and Chrome 17 Canary will also be out...and so on. They run in parallel. I believe Firefox has something similar.
I'm sure they're working on it. :)
Being employee #1 is fine, but you should be asking questions like 'how much money do you have?' and 'when will it run out?'

I've been employee #1 and in the position of having to find another gig due to the company running out of money. It sucked, but I was prepared for it since I knew what our runway was and what our situation with funding was.
How do you know he wouldn't say that in person?
If it's a multi-frequency chip it might not matter as much...
Oh get over your pompous self. "Low-level" terrorists my ass. Terrorists kill people. Anonymous disrupts services and blocks access.

That you're likely an American, directly funding the current killing of tens of thousands off people every year (still) in the fictional hunt for WMDs, and you're condemning protestors is farcical.
The point is that signing a contract for personal liability negates the incorporation.