skysight-inc/HackerNews huggingface dataset:
Probably RCS http://www.gnu.org/software/rcs/; It's a fact that it used CVS, then SVN at some point (see https://gcc.gnu.org/viewcvs/gcc/branches/CYGNUS/, a branch created by cvs2svn, a migration tool)

EDIT: Apparently all previous history was lost when they implemented CVS, circa 1997. We could always ask someone in the oldest maintainers file available (https://gcc.gnu.org/viewcvs/gcc/trunk/MAINTAINERS?revision=1...) and have the real answer.
Wow - the second post about Grooveshark to hit the front page today. The other one was deleted by the poster:

https://news.ycombinator.com/item?id=7975137
> The website is pretty clearly operating across state lines.

Why is that so clear?

It's fairly easy to create an infrastructure that directs users to servers solely in their state. Prostitution is a fairly local affair.
Reading the pastebin text, it seems a little petty and most of all a bit of a big emotional rant.

So the author does not agree with the valuation, many people do not agree with valuations of companies, in fact companies which lose money in some situations still have high evaluations as the valuation is market driven in some cases.

People getting fired, well that happens all the time. Lawsuits happen to companies, HR not getting fired happens, companies hiring for growth happens.

The problem with the author is the way they have stated their case, there is common problems framed with insinuating remarks which are further compounded by a use of profanity. Not to say if the post is true or not, but the author could have done a great deal better to establish credibility.
I agree with you. If you can't be bothered asking me the questions in person, I can't be bothered answering them. That's the social contract.

I've already written a cover letter that responds to the points in the ad; if they can't prescreen sufficiently using that then they need to work on their ad.
Don't agreements like this typically include language to the effect of:

"This agreement is entirely enforceable under the laws of the state of ____, under the jurisdiction of a binding arbitrator chosen by the employer, except for injunctions which are handled by the ____ District Court in ____ County?"
Like a couple of others on here. Not a programmer, but have read HN for at least a few years.

Location: Qatar
Remote: Yes!
Willing to relocate: No
Technologies: Marketing/Communication/HR side tech and HRIS systems
Email: nalani[dot]still[at]gmail[dot]com
Dual US/UK citizen
So ... Earth's moon has about the same surface area as Africa? This never occurred to me.
I'm more concerned with the fact that the function is more than 700 lines long.
Location: San Francisco / Los Angeles

Remote: No

Willing to relocate: Yes.

Technologies: Ruby, Rails, JavaScript, Node.js

Resume: Available upon request

E-mail: solitarybookclub@gmail.com (e-mail will be forwarded to my primary address)
I have watched on TV Ian Chappell narrate this same story, as an incident between him and Bradman when they met at a party celebrating Bradman turning 90. Very likely apocryphal.
They key problem is the number of combinations of inputs, outputs and state. And since its difficult to set up state correctly in such an api-based test, then the tests invariably end up using the api to initialize state. So that means we're dealing with the permutations of inputs, outputs and state, not merely the combinations.

Basically anything more complicated than a "unit" is impossible to test for every permutation and as a result you get bugs when things happen in production that nobody anticipated a test for.

In short, been there, done that. Yes, way easier to write less tests that don't test everything. Witnessed plenty of six figure+ bugs as result.

Meanwhile, if refactoring means breaking a load of tests then you're doing it wrong. TDD is actually pretty hard to learn and it seems to me most people give up when the have to refactor code that they've tested internal details. Given their knowledge they conclude TDD is bogus, rather than wonder if perhaps their tests are bogus.
"Discovered" this guy due to some reddit post. Now reading his "Systems Performance" book which should definitely be required reading for performance engineers.
Actually reload has been replaced by LRA for x86/x86_64 in GCC 4.8 and work is ongoing to bring LRA to other targets. So it shouldn't be forever.
I still think self driving cars are the wrong solution to problems that exist.
This, plus the stucture stays very readable even if for any specific reason a test clause has a very long line.
How CVS’s Customer Service Investment is Expected to Cost CVS $2Billion in Sales
How CVS’s Customer Service Investment is Expected to Cost CVS $2Billion in Sales
I guess we should also should include that with every Linux kernel release too. The US government has funded a lot of publicly available security technology that you may not even be aware of, even through the NSA (SELinux).

It is a good thing the US government supports these things.
Lets address your concern by talking about security and probability for each of those issues.

Credit card thieves in Comcast vs in TOR. Given the number of employees who has remote access to customers routers (ie support), sysadmins that has remote server access, and personale who has physical access to switching equipment, whats the risk that one of those people has a criminal record? This will always be non-zero, and one can never actually test it.

In TOR, this risk can be tested[1]. Exit note can be probed by sending unique credit card numbers or other profitable personal information, and then observed by seeing what the node owner does. If they act on the information, the node then get blocked. You can not do this with Comcast since your identity is known to the personal of Comcast.

The NSA threat, as talked about, is reduced by using TOR. Doing statistical analysis is in theory possible but in practice very hard. Out of all the Snowden leaks, not a single one present this as a ongoing work happening. Non-tor traffic analysis is however presented as business-as-usual and should be assumed to happen at every point in the network.

Last, the HTTPS Everywhere you mention is a direct answer to the SSLstrip for the most commonly used websites. Claiming it is implemented backwards because it uses a blacklist is a bit unfair, since blacklist and whitelist each has their own tradeoff in security. HTTPS Everywhere has no false positive and protect against the common threat, but will be vulnerable against uncommon ones. If they had gone with a HTTPS-only approach, it would have caused a extreme amount of false-positives, and users would have turned it off. This trade-off (security vs false positives) is commonly the distinction between user products and server products.

KB SSL Enforcer do not protect against sslstrip and MITM[2] for new installations. If the Tor Browser Bundle included KB SSL Enforcer, it would worsen the security of the Bundle compared to HTTPS Everywhere, and would be counter to the design. Rather than leaving no records of the sites you go to, KB SSL Enforcer have to record and permanent store it.

[1] http://www.slideshare.net/FreeLeaks/exposing-malicious-tor-e...

[2] https://code.google.com/p/kbsslenforcer/wiki/FAQ
Has anyone figured out yet which parts of a human can be compressed in a lossy way without anyone (especially yourself) noticing?
It's still there in the latest OS X: http://i.imgur.com/40DGTXo.png
You could say exactly the same about OpenSSL - it's not a good argument.
You could pull out boolean subexpressions and give them descriptive names and still use one if statement. It's even in the Google C++ style guide I believe.
I'm sure a good optimizing compiler like GCC would optimize out repeated expressions in conditions ;) (perhaps not if they're declared volatile(?))
More info here: http://500.co/invest

"To learn more about our fund offerings, please provide us with some information about yourself and your interests ... If you are selected, you will receive access to our investor presentation and related fund materials via SeedInvest..."
Don't take me wrong, I really appreciate Khan and I've learned quite a bit from his videos, but I am not seeing the technical challenges in running the website. My opinion is the challenge with Khan's academy is not a technical one, but how to scale the teachers/presenters. Khan is a great teacher, very knowledgable and engaging, but how do you find people like him to take over the other subjects.
I understand that California is not for everyone for any number of reasons but if you stay in CA non-competes are basically irrelevant to your career.
Invest in 500 Startups
Australians, The Hot New Players in Silicon Valley
Agree that the comments page on HN could be more useful.
Because they don't do that.

And even if they tried, there is no way to prevent users from just across the line in Alabama from searching for prostitutes in a bigger city in Georgia (geolocation based on IP address is not always that accurate).

But let's say the site could someone manage to ensure that no interstate commerce was going on between users--there is still interstate commerce happening because the company is operating across state lines by paying for all those servers/generating add revenue from all the users.

Furthermore, did you read the rest of my comment? None of the above really matters because a bunch of sites engaging in intrastate commerce can still have a substantial cumulative effect on interstate commerce.
This doesn't surprise me. And I am actually quite curious, because after almost two years working at Amazon.com I quit, thinking Amazon.com was Google was Every Corp > 1000 headcount.

Since then, I haven't had the stomach to interview or consider another job. After much reflection, I think it all had to do with Amazon.com, the working conditions, and the tone of the place.

I got it in my head that all corporate jobs are basically like Amazon.com: you sign away all of your intellectual property rights, accept working on things you don't control and take home a nice, better-than-almost-everyone paycheck to wash it down.

I could tell strange stories of working at Amazon.com (I was in a non-traditional engineering role) but they seem more or less pointless.

How does someone go from working at Amazon.com to a small workplace, with passion and freedom? I have floundered! And the oxygen is running out.

Anyway, I wouldn't recommend working there.
Neal Stephenson's Cryptonomicon frequently references "Finix" ("Finux"? something like that), an obvious stand-in for Linux. IIRC, Stephenson chose the pseudonym to avoid geek rage if he mis-reported some tiny detail of Linux.
I just realized the Mixpanel issue might just be because I use AdBlock...
Semantics3 (YC W13) is looking to hire data scientists in Bengaluru
We semantically interpret and process terabytes of data everyday. This requires two broad skills: a) the ability to work with large-scale search indices and databases, and b) the ability to build and enhance algorithms that make sense of this data, in particular, for product matching (product disambiguation/record linkage). We’re looking for a data scientist who can meet these needs.

Preferred profile:

- Has worked with information retrieval tech (Lucene/Elasticsearch).

- Is comfortable with NoSQL databases and scripting languages (Perl/Python).

- Is familiar with NLP and ML techniques, but recognizes quick and simple approaches where they exist.

- Believes that more data + heuristics can sometimes outperform fancy algorithms.

- Has a Bachelor’s/Masters/PhD in Computer Science/Math/Physics/EE/ME from a top university.

- Notable previous work experience in a challenging environment, ideally in e-commerce.

- Can deal with the uncertainty and messiness that comes hand in hand with large datasets.

- Can slot into an environment where respect is earned by shipping results.

==

Look forward to:

- Being a critical member of a small and motivated engineering team.

- Pushing your programming and analytical skills to the limit.

- Coming in contact with new technology that may yet be years from becoming mainstream.

==

<To apply for this role, send in your resume at jobs@semantics3.com>
Now I can see my balding head all the time...
Wthr, An Innovative Weather App for iOS
Tor itself has a nice built-in method of authentication you can use. I don't know of a good howto, but it's documented in the man page. Search for "HiddenServiceAuthorizeClient": https://www.torproject.org/docs/tor-manual.html.en
In prev discussion (id=7972941) many discussed mixing new and top posts and how they should be visually differentiated, etc. But there may be a simpler solution.

First, make “new” page default for registered HN users, “front” page for visitors not logged into HN

Yes, but having separate 'new' and 'home' pages would still incentivise me to mainly look at the home page, and ignore all new posts. I like the idea of mixing 'new' and 'top' posts on a single page, without any specific visual cues to differentiate them (except age, # comments, # votes)
Except when they don't.

Because, sometimes, they won't.

I'm sorry to say so

but, sadly, it's true

that unknown

or expired link

can happen to you.
Emscripten's JavaScript libc
In theory yes, in practice I mostly disagree. The ideal is to test everything, the public API and all the internals. But there are only so many hours in the day so if you have to choose (which most of us do) then the best place to put the majority of the testing effort is in the public API. The reality is that there will always be bugs...always. While 100% bug-free is a valiant goal, it is pretty much impossible to achieve in a complex system. However what is achievable (or more achievable at least) is being almost completely bug-free at the public API level. From a business point of view, this is the only thing that really matters because it is the only thing your users and customers care about.

In your fruit basket example, there are two fixes for this. Either improve the public API tests to verify that an hour later the file is still there. Or you use a storage technology where you can assume it will work correctly (Postgres, S3, etc) and then have a code review.

There is definitely an exception to "only need to test the public API". That is when a very complex component has to be built from scratch or almost scratch in order to support the public API. For example, I personally need to build a Lucene-based search server (Solr and ES don't fit my use case). While I shouldn't need unit tests for Lucene itself, I do need unit tests to verify the threading model, file structure, and couple other things I write from scratch are correct because the complexity is so high and I don't trust myself or anyone else to write it correct the first time.
I am not arguing against the integration test point, but I do see a value in unit tests.

When I write/modify a piece of code, I of course must see so it works. I run the new code, feed in some data and see the results.

If I separate UI and backend/model, I can just write code that feed data to the model to see so it works (instead of doing it ad hoc, by hand). Then I save that as a unit test. It is part of the documentation too (a use case).

Cheap, easy and with good value for effort. (Depending on problem domain.)

Edit: I can see where the "test induced design damage" comes from, mocking is bad, but I think code also often get better when it is made testable (dep injection, think about fan out/in, etc)
I'm not a fan of down-votes, but I will try to (kind of) refute your central point according to the argument pyramid. (Not fully disagreeing with you, just some thoughts on the matter).

The central question is: did he really knowingly sign a non-compete agreement and is it lawful in the jurisdiction?

Yes, he signed the contract, which was likely a 20 page standard issue paper that was mostly written by Amazon lawyers in small print.

Now most of us don't send a copy of employment contracts to our layers and discuss it with them for hours before signing (that's kind of expensive).

That's why there are some limitations on what can go into a contract in some places (at least in Europe, but I assume the U.S. has something similar). For instance they can't write in there that you will be their slave, providing unpaid work without the ability to quit, be beaten as motivation and lawfully enforce it, even if you sign the paper.

Other things need to be explicitly clarified to be accepted at court. For instance, if a big software corporation would add a clause to their license agreement on page 25 that your house belongs to them if you click on "I Agree", it would most likely not hold ground in a court. If they explicitly explained this to you (with a few witnesses), it might be heard in court.

The question here is (and it's far from clear cut) is if this contract holds it's ground in court.

Back to the central point: this means, that Amazon might have to prove that they made a good effort to clarify this clause in the contract explicitly and it's lawful in the state he worked. That's up to the court to decide.

Now if they can prove that they did make a good faith effort to clarify his contract, he agreed and then went on and willfully broke it, then he is in a troublesome spot.

INAL, this is not an advice for anything and I'm not liable for any of the above.
I'm an Android "fanboy" and I finally decided to try an iOS device
Like Docs, Maps, blogger and youtube?
"Call me old-fashioned, but running a business that makes money is not the worst thing in the world."

Are you kidding me? This is the whole point. Regardless of the funding, the goal is for a business to be self-sustaining. A company that relies on external funding is no company at all.

So let all the Zuckerberg-wannabes go after the funding and end-up with 1% stake with 0% authority... I'll settle for building the business, creating the processes and systems, attracting and supporting the customers, and keep my 100% thanks.

This is why Warren Buffet hates tech-stocks. Everyone thinks there's a different metric in tech. There isn't... self-generated cash is king.
> What if the internal code incorrectly stores the fruit in a temporary file?

Genuinely curious - how would you write a lower-level unit test to account for this?
If my "testAddFruit" method directly hits the temporally flimsy datastore, how is that any better than the API doing the same, albeit through multiple abstraction tiers?
Black prom dresses
black prom dresses
Haha, indeed. Who would ever have thought to put a picture on a white background? Gotta protect that IP!
Erm this smacks a little of absolutism. In many cases you'll definitely want to test at a method level - if the behaviour of a single method is complex but its not part of the API, if you want to test it properly, you'll likely still have to have a similar number of unit tests (to properly pinpoint a bug), you'll just need to move them up to the API level - and furthermore, the tests you need to come up with are far more complex, as they have to anticipate the outputs of each function call as well (in order to obtain the same coverage).

It's correct that by reducing your number of units and making them more broad scoped, you potentially reduce the number of undetectable faults you are catching (but need not), but you also make crafting the input that detects the remaining faults much more difficult.

The correct approach is (it seems obvious to me) to mix the two. Don't force tests to be on a per-method basis, but also don't neglect to individually test those methods that can be better tested by individual testing. It seems like common sense - following a policy such as this so rigidly clearly leads to either wasted time and inferior APIs or missed test cases - the former I believe the OP has discovered already, the latter I'm sure they'll discover in due time.

http://www.quickmeme.com/img/0f/0fb4fa35fad1b9ed112dc7584f47...
Sounds like you need to spend some time with go!
If you want a single identity why do you have five active accounts?

I have multiple google accounts because I want separate google identities.
Are you based in the US?

Unfortunately, I am not, so I cannot assist with leads.
I might have an even better idea, maybe easier to implement as well:

Make it socially acceptable to add an abstract (or a tldr) as the first comment.

Something along the lines of:

"""Can data driven customer acquisition replace metrics for underfunded crowdsourcing frobs? Article says yes.

Data heavy with some interesting observations nicely presented. """

Or:

"""Submitted mostly as an example of breaktrough frob design. Hoping for comments from someone knowledgeable on frobs and frosb.""" (Hi, keep it honest : ).

The rationale for not having an abstract or tldr is summarized in the faq :

"""How do I make a link in a question?

You can't. (This is to prevent people from using this method as a way of submitting a link, but with their comments in a privileged position at the top of the page. If you want to submit a link with comments, just submit it, then add a regular comment.)"""

This suggestion should work nicely along with this intent: you are free to add extra info but you don't get a privileged spot on top of the page.

(Edit: posting from mobile device, first version just to get it out)
As I am sure you're aware, correlation is not causation. But you didn't say it. Plenty of studies suggest that it's how the cholesterol is carried in the blood that matters and this isn't just a matter of HDL and LDL; the type of LDL matters too as do triglycerides. Another important factor is inflammation i.e., high c-reactive protein levels need checking out. And of course other factors may be significant as well.

To put it politely, pertinent questions remain regarding the data which Ancel Keys picked to support his high fat = heart disease hypothesis.
Companies seem to want to view employees as somewhat disposable and have shifted the burden of taking care of somebody long term (pensions, retirement, career progression etc) onto the employees themselves. But in doing so they're encouraging labor mobility, and seem strangely shocked to find out that employees would take with them the expertise, history, and network of contacts that they had accumulated and move that value somewhere else.

It's really interesting how they have resorted to strong arming their engineers with these shot in the back non-competes, and couple it with salary collusion and hiring agreements. Throw in the golden handcuffs (that turn into golden dental floss after a few funding rounds -- long after they've gotten their 60-70 hour work weeks out of the true believers) and you see how they are trying to stymie that labor movement.

It's really a wonder that technology workers haven't started forming some sort of union.
Well, you could always go with "most of the body". I mean, the peripheral parts could be almost regrown from source, with the additional benefit of leaving behind many years of injuries you've picked up. My knee certainly agrees with this sentiment right now :)
Internally, employees at Amazon have to go through an extensive review process to contribute bug reports, blog posts, or any activity involving sharing code. And for the oddest reason, any game development of any sort is absolutely forbidden.
established accounts are allowed to use tor on HN. If you make an account over tor, its posts will be killed for two weeks, then it will be a normal account.
now he'll have two problems!