skysight-inc/HackerNews huggingface dataset:
I wrote about this four years ago when Obama chose Biden as his running mate:
http://news.cnet.com/8301-13578_3-10024163-38.html

Note one House committee did vote in the 1990s to ban the "manufacture, distribution, or import of any encryption product that did not include a back door for the federal government," but that bill failed to become law:
http://news.cnet.com/8301-31921_3-20032910-281.html

Excerpts:
Biden's bill -- and the threat of encryption being outlawed -- is what spurred Phil Zimmermann to write PGP, thereby kicking off a historic debate about export controls, national security, and privacy. Zimmermann, who's now busy developing Zfone, says it was Biden's legislation "that led me to publish PGP electronically for free that year, shortly before the measure was defeated after vigorous protest by civil libertarians and industry groups."
...
After taking over the Foreign Relations committee, Biden became a staunch ally of Hollywood and the recording industry in their efforts to expand copyright law. He sponsored a bill in 2002 that would have make it a federal felony to trick certain types of devices into playing unauthorized music or executing unapproved computer programs. Biden's bill was backed by content companies including News Corp. but eventually died after Verizon, Microsoft, Apple, eBay, and Yahoo lobbied against it.
A few months later, Biden signed a letter that urged the Justice Department "to prosecute individuals who intentionally allow mass copying from their computer over peer-to-peer networks." Critics of this approach said that the Motion Picture Association of America and the Recording Industry Association of America, and not taxpayers, should pay for their own lawsuits.
...
The ACLU also had been at odds with Biden over his efforts to censor bomb-making information on the Internet. One day after a bomb in Saudi Arabia killed several U.S. servicemen and virtually flattened a military base, Biden pushed to make posting bomb-making information on the Internet a felony, punishable by up to 20 years in jail, the Wall Street Journal reported at the time.
...
Thank you for this information. And your statement "Public food should be open source". That's something worth discussing as a society. Food is so important...
What do you think about Genetic Engineering for Humans. Is that also the future? We can cut medical costs for everyone by engineering humans to be immune to many known diseases. And better stuff.
Very good point, it seems like a perverse reverse incentive. However I don't think that the earnings of a given field speak to its "value" - as I'm sure any teacher would agree.
I tried this tool on a few texts and it recommended some fixes on ambiguous and redundant words. It didn't change the style as much as it improved the clarity and comprehensibility of the text.

I think you're overreacting.
American, also not a lawyer.

1. Having the domain is a good first step. As you can verify the registration date, you can claim copyright. (not trademark) This might be enough protection.

2. Sortof, but at a cost so high, I can't imagine why they'd do it in the first place. You'd also win any legal fights in the end, but at great cost (Lawyers ain't cheap).

Most will simply steal the idea and re-brand, not try and usurp your fledgling market. (see Facebook Poke for an example of destroying the little guy)

Your primary concern should be if someone else has already registered a similar name, and _they_ have priority over you.

4. Start with a Poor mans copyright, by mailing a certified letter to yourself with the outline of the idea, domain, pitch, etc. As it's date-stamped by the government, you can have it opened in court to prove you came up with the idea first. Used by authors and screenwriters seeking claim to the original ideas they generate, so no one can copy the idea without compensation.
This is a really good and interesting question, and it's one I've been struggling with myself.

The problem boils down to this: TDD makes your software more maintainable (if you do it well) and it lowers your cost of development. However, it also takes significant time and effort to figure out how to test-drive a technology for the first time. Everybody can TDD a Stack class; TDD'ing a database, or a web server, or JavaScript [0] is a lot harder.

So the answer seems simple: use TDD for the parts you already know how to TDD.

But it's not so simple! It's much harder to add tests to existing code than it is to TDD it from scratch. Sometimes, it's flat-out impossible. The expense is so high, there's a very good chance that you'll never get around to adding tests to the un-TDD'd code. It will hang around causing bugs, preventing refactoring, and sapping your agility forever, or until you rewrite... and a rewrite of any significance will halt your company in its tracks, so you won't do that.

So the reality is that, anything you don't TDD from the beginning, you'll probably never be able to TDD. Companies that go down this road find themselves doing a major rewrite several years down the road, and that's crippling [1].

There's another wrinkle on top of this: manually testing code and fixing bugs is expensive. Once your codebase gets above a certain size--about six developer-weeks of effort, let's say--the cost to manually test everything exceeds the cost to TDD it. (The six weeks number is a guess. Some people argue it's less than that.)

So the real answer is a bit more nuanced:

1. If your MVP is truly a throw-away product that will take less than six weeks to build and deploy and you'll never build on it after that, use TDD only where it makes you immediately faster.

2. If your MVP is the basis of a long-lived product, use TDD for the parts you know how to TDD and don't do the parts you don't know how to TDD. Be creative about cutting scope. If you must do something you don't know how to TDD, figure it out and TDD it.

3. It's okay to be a bit sloppy about TDD'ing the edges of your app that are easily rewritten or isolated in modules. But be very careful about the core of your system.

That's my opinion based on 13 years of doing this stuff, including building five successively-less-minimal MVPs over the last nine months for my JS screencast. The first three MVPs were zero coding, the fourth was a throw-away site, and the fifth was TDD'd with aggressive scope cutting to minimize the number of technologies that had to be TDD'd.

[0] Shameless plug: I have a screencast on TDD'ing JavaScript that I'll be opening up to the public, on a subscription basis, in a month or so. http://www.letscodejavascript.com .

[1] Rewrites are crippling: See Joel Spolsky's "Things You Should Never Do, Part I." http://www.joelonsoftware.com/articles/fog0000000069.html (There is no Part II, by the way.)
Everyone seems to focus on the fact that she was 103. That's not her greatest achievement. As a jewish woman she faced many obstacles in her career, was forced to work at home, immigrated to the US and finally discovered NGF, for which she won the Nobel prize. She was also a senator for life and a star scientist in Italy.

http://en.wikipedia.org/wiki/Rita_Levi-Montalcini
"OS" is a vague term, but for example

> Process management, threads, interprocess communication, memory management, the file system structure, input/output, network primitives... Aren't these responsibilities of the operating system?

they are, and they don't need to be in the kernel, which would be enough to say that a kernel is not an OS.

Even ignoring stuff like user space drivers/FS/network/threads, you usually use some user space APIs to interface with the kernel.

And maybe you need something to actually be able to launch programs, an init system, some login process etc..

FWIW, the definition I had in school(s) was more loose, on the likes of "the OS provides the basic functionalities to run and control programs".
TDD is good for some things, terrible for others.

TDD's great when what you're working on is easy to test, like your data backend for your application.

It'll vary based on your product of course, but in my experience I've found the frontend to be the big time sink in development. Using TDD for contemporary frontend development is, in my opinion, a big time sink since the cost/benefit ratio of frontend testing today is way too high.

tl;dr use TDD for your backend (data model invariants) and hack your frontend as quickly as you can (on top of a decent frontend stack so you don't get that messy).
Arch with xmonad as my window manager (http://xmonad.org/)
I'd add a friendly amendment: CALEA was intended to be a first step, a
"beachhead," toward domestic controls on encryption. The fact that the second step was not successful came despite efforts by Biden, the FBI, the NSA, etc. -- not because of them. See below.

http://news.cnet.com/8301-13578_3-10024163-38.html
"Joe Biden made his second attempt to introduce such legislation" in the form of the Communications Assistance for Law Enforcement Act (CALEA), which was also known as the Digital Telephony law, according to an account in Wired magazine. Biden at the time was chairman of the relevant committee; he co-sponsored the Senate version and dutifully secured a successful floor vote on it less than two months after it was introduced. CALEA became law in October 1994, and is still bedeviling privacy advocates: the FBI recently managed to extend its requirements to Internet service providers.
CALEA represented one step in the FBI and NSA's attempts to restrict encryption without backdoors. In a top-secret memo to members of President George H.W. Bush's administration including Defense Secretary Dick Cheney and CIA director Robert Gates, one White House official wrote: "Justice should go ahead now to seek a legislative fix to the digital telephony problem, and all parties should prepare to follow through on the encryption problem in about a year. Success with digital telephony will lock in one major objective; we will have a beachhead we can exploit for the encryption fix; and the encryption access options can be developed more thoroughly in the meantime."
Is there a particular aspect of adult learning that you're most interested in? It's a very large field, but one that I got rather obsessed with. If you have some specific areas of interest (or if you'd simply like a reading list), my email address is in my profile.
It is true that sense of congress resolutions are not law, and just an 'opinion of congress'.

Just for context of what Biden's opinion was at the time, here is the 'meaningless sense' that appears to have originated in his bill, S-226, from 1991.

SEC. 2201. COOPERATION OF TELECOMMUNICATIONS PROVIDERS WITH LAW ENFORCEMENT.

It is the sense of Congress that providers of electronic communications services and manufacturers of electronic communications service equipment shall ensure that communications systems permit the government to obtain the plain text contents of voice, data, and other communications when appropriately authorized by law.

http://thomas.loc.gov/cgi-bin/query/F?c102:1:./temp/~c102sT9...:
Check https://openhatch.org/

There are a few end user apps written in Python that are seeking contributors (Serpentine, MV3D...)
The Case For Bullshit Metrics
How The Huang Brothers Bootstrapped Guitar Hero To A Billion Dollar Business
Comcast exposes customer billing address to anyone on your Internet connectiaon
You wrote about this incorrectly; you cited Biden's language, which begins "It is the sense of Congress that", and then wrote "Translated, that means turn over your encryption keys", which it plainly does not mean, because sense-of-the-Senate language doesn't create law.

Then, you wrote "Joe Biden made his second attempt to introduce such legislation in the form of the Communications Assistance for Law Enforcement Act (CALEA)", although Leahy sponsored CALEA. You also failed to note that the only mention of encryption in the bill exempts providers from responsibility for providing plaintext, instead casting CALEA as attempt to ban encryption, which it was not.

I would at this point like to ask you, as a journalist who claims to have covered this topic in detail, what evidence you can present that Joe Biden is "staunchly anti-cryptography".
I initially thought the question was
"Do we ask our MVP to use TDD ?"
-.-
i'm a taiwanese and i take offense with that
I'd use a lightly blinking notice box at the top of your screen, just below the header. Let it disappear when not clicked within 5 seconds or so. Give a teaser, with a link to take the tour around new features. Only do that when you have several that are worth the time to learn about.
BTW - I'm from a marketing/sales background and just getting into IT/Comp.Sc. maybe we can learn from eachother? My email is in my profile.
The key question here is, are you building a quick and dirty prototype, or are you building an MVP? MVP doesn't mean a garbage prototype. Depending on what you're doing, an MVP could still take significant time to build (and your MVP would take 1 month vs 3 months for the "full product.")

IMHO, if you're worried about supporting and maintaining your app, and concerned about your users not having a buggy experience, you should TDD it.
When The Chasm Comes Back and Hits You In The Face
Please fix the indentation in the image. I was so confused by it until I noticed that "location" and "locate" are both properties of the person object. They should both be indented the same.
Again, worth noting that Biden cosponsored a bill less than a year later that (a) provided for lawful intercept of telecommunications while (b) explicitly exempting providers from a requirement to provide plaintext.
Although Biden's amendment by itself wouldn't have outlawed SSH, it was enough to make programmers see the writing on the wall. A bill with domestic restrictions on encryption was approved by a House committee in the 1990s, and Biden's bill was what prompted PRZ to release PGP, as PRZ himself said at the time. See:

http://news.cnet.com/8301-31921_3-20032910-281.html
In response to lobbying from the FBI, a House committee in 1997 approved a bill that would have banned the manufacture, distribution, or import of any encryption product that did not include a back door for the federal government. The full House never voted on that measure.
Learning Vim isn't that hard - it does take a few days of study to learn the core idioms of movement and manipulation, but once you wrap your head around it the rest is just practice and building muscle memory.

As far as "actually productive," having a better editing/writing flow is one of the biggest productivity enhancements I've encountered in my programming career.
> something must be broken if the customer is getting billed due to the environment beyond their control.

This is what happens when you debate random tangential topics online while hung over.. so basically I had no point to make, and you made me realize NAT is a pragmatic solution to the imaginary problem I'm complaining about.

> Presumably the application processor only awoke when a kernel timer fires

And of course for the reasons you point out, this presumption was obvious nonsense. :) Now I'm not sure what caused the behaviour I saw on the Dream.
http://willsmidlein.com/blog/tech-trends/
Not exactly. Most Android devices come with a very simple shell named ash, but it's no relation to busybox's ash.
My biggest issue with "entitlement culture" is the phrase itself: it's loaded language, thinly veiled propaganda to make opponents look bad. The creationists and NeoCons use the same tactic all the time (and freely admit to it being a tactic they use on purpose; look up their policy documents sometime). "Death tax" instead of inheritance tax, "taxpayer money" instead of public funds, etc, etc. "Framing" is another good topic to look up along these lines.

What I want to know is why creators of content feel "entitled" to get paid? Sure, it'd be nice to get paid every time you do work, but that's not how the world works. Getting paid every time someone makes a copy (where virtually no work is done, these days) was a fluke of history that people shouldn't rely on either. Note that I'm not justifying copyright infringement (not "piracy", another loaded term), but "intellectual property" has no basis in reality, and a very thin one in what we jokingly call law these days. If a creative work is so important, then it's important enough to preserve, and that just about requires unfettered access, especially since there is no requirement to submit a non-DRM'ed copy to the copyright office anymore.
The question here is really "what's the test?" You have to reailze the MVP _is_ the test.

For a startup, customers are how you pass the test. Anything else is a red light. So in the most important way possible, as long as you have no customers, you have a test which is failing.

This is important because the maintainability you're looking for in a startup is your relationship with the customer. Manage that and the rest takes care of itself. If you are already in a business, yes, "maintainability" means writing code that will last. But if you've just got an idea or a dream, you've got nothing worth maintaining. Nor will you ever.

Put differently, your technical debt can never exceed the economic value of your code, which in a startup is extremely likely to be zero. (Different scenario entirely for project-based work for ongoing businesses, which is why TDD makes so much sense in that scenario)
Automattic Canvas Fireworks
I'm from Canada, last year we had an omnibus crime bill that included an amendment for government to warrantlessly track
online activity which they defended as a way to track pedophiles.

http://www.thestar.com/opinion/editorialopinion/article/1131...

In the USA, this wasn't an amendment but would have affected far more than just predators: "Protecting Children from Internet Pornographers Act of 2011".

http://en.wikipedia.org/wiki/Protecting_Children_from_Intern...

In the UK, there is the snoopers bill for monitoring online communication, choice quote [3]:

> "Criminals, terrorists and pedophiles will want MPs to vote against this bill. Victims of crime, police and the public will want them to vote for it. It’s a question of whose side you’re on,” said Home Secretary Theresa May.

http://rt.com/news/uk-snoopers-charter-may-276/

There is certainly a pattern of using the "4 horsemen" to pass bills attacking internet freedom that affect all citizens not just the criminals.
In Peter Watts' scifi novel "Blindsight"[1] there is a description of aliens which could program their bodies on the fly to move only during the saccades of one human observer in order to hide themselves[2].

[1] https://en.wikipedia.org/wiki/Blindsight_(Watts_novel)

[2] http://www.rifters.com/real/shorts/PeterWatts_Blindsight.pdf page 236
I think it very much depends on what your MVP is, what your goal with it is.

My stance here is where the goal of the MVP is to get investment money. You're not showing your MVP to random users. You want to build something that "works" quickly, then get money to build it "properly". You have a good idea and you want to attack a certain market; but, you don't want to spend year(s) building a product and hope you can grow slowly. Your aim is to prove to investors that; you're a good team, you have a solid concept, with money you will gather a team and build this product.

In this case, I think you can(/should?!) skimp on the unit tests. The code will be thrown away after a few months of its inception.

There are of course many different MVP situations, this is just one small avenue.
"nobody"? Asus Transformers are a very popular option for Android tablets, in part because they have keyboards and touchpads and a full sized USB port for easily plugging in mice.
Would you prefer to bind that ['this'] yourself?

Certainly. Why should some state be teleported in magically while other state (the argument 'e' in the above example) has to ride the bus? Does it belong to a different class of Being? I don't think so. This forces me to spend precious brain cells remembering which things go in which buckets and what the rules are for accessing the buckets - i.e. busywork - rather than the problem at hand.

The easiest thing is to explicitly bind to just that state you need and ignore everything else. That's more or less what the argument "e" offers: it's a bag of all the goodies you might need while handling your event. Clearly, therefore, the DOM element emitting the event should be available through that same mechanism – and as you generally can get everything you need in that department through things like e.target, I find it simplest to remain blissfully ignorant of 'this'.
Personally I wouldn't, but my opinion doesn't matter.

Does TDD help you? If so, use it! If not, don't! The whole point of an MVP is to ship something ASAP. Do whatever helps you do that.

Personally I've found TDD to be a tremendous waste of time for most things, but I know some people swear by it. It's your product. Git 'er done in whatever way you've learned to get things done.

Edited to add: People talk a lot about TDD leading to more maintainable, less coupled code. There's more than one way to skin a cat—not using TDD doesn't necessarily doom your codebase, and using TDD won't necessarily save it. Like I said, do whatever works for you.
We have a similar problem here too (Australia). Other Politicians from the opposing party spend time nitpicking things that were done in the distant past.

It becomes a big deal when anyone does a 'backflip'. I don't have proof, but I would wager that certain politicians stick to supporting things they no longer believe in, just to avoid this kind of thing.
I never identified any workaround. In fact, I never even identified this paywall. I just have my browser set to throw away cookies on exit, except for a small whitelist of sites I want to stay logged in to (Opera can keep per-site preferences, but even before I found out about that feature, I preferred not to keep my cookies around forever). Assuming that's the "workaround", it appears that I have never read more than 10 NY Times articles per browser session, since they started doing this.

I also keep a rather extensive blocklist of URL-patterns I don't need my browser to load, ever. It took quite a while before I noticed (on a friend's computer, about 1.5y ago) that YouTube makes you watch ads before a video. I actually have no idea how that particular URL-pattern got into the blocklist, since I honestly hadn't seen those ads before. I suppose I was messing around with the webdev tool one day, noticed some resources that seemed unnecessary, I disabled them, videos continued to work fine, and forgot about it.

I realize this places me securely in the second segment, of course.
That's an impressive timeline. How many people is "we"?
The actual AMA will go-live on Jan 3rd at 5pm GMT. However David Braben and Frontier Senior Producer Michael Brooks will be on answering questions when they can in the lead up to the AMA.
What an awesome concept! Thanks for the link, I think I'll be adding this to my reading list.
great work! btw, is there a versioned json toolkit?
Graph of programming languages people used in 2012
> the browser market is very competitive right now.

The important bit is "right now". It used to be competitive before IE6's stranglehold. And today, we can see a single implementation rapidly rising in marketshare, if that continues then we may have a non-competitive marketplace in the not-so-far future.

In fact already right now WebKit has a dominant position in mobile, and many sites only work in WebKit.

So even if the market is fairly healthy right now, we still need to be careful that doesn't change. The current trend hints that it will.
Google Chrome blocks access to Twitpic for Malware risk