skysight-inc/HackerNews huggingface dataset:
Isn't the number used later in the article incorrect too?

The article says: "Thus the real impact is constrained to 1/56th of the overall shuffle shards."
Shouldn't it be 1/28th?
It's 8*7 / 2 since the permutations "shards x, y" and "shards y, x" are the same as far as fault-tolerance is concerned.
No, your assertion doesn't follow logically. For instance, during the course of a trial, an antagonistic witness can be treated as hostile, giving examining attorneys more leeway in what questions they get to ask. Or, a dishonest witness can be treated as if all their statements were untrustworthy in jury instructions.

Being punished for hurting a prosecutor's feelings is not the same as being penalized for obstructing the proceedings of a court case.

This decision spends tens of pages applying the law to the facts of the case, and deciding against Levison.
Generics generics. I've written Go code for 40+ hours a week for 10 months and only missed generics a couple times for some minor functionality.

That, and they are not anathema to Go. The Go devs want to implement generics, they just have more important things to do right this second.
The Ubuntu Edge was designed around a similar multi-purpose idea, though it wasn't physically modular:

http://en.wikipedia.org/wiki/Ubuntu_Edge
Part of the reason might be that some manufacturers offer generous sales bonuses to store staff as part of their marketing effort. It's very likely they're doing what's right for them rather than for the customers.
As the article said. Disasters have more than one cause, almost without exception.

Then, quality minded people just know that they must correct ALL the causes, because they may lead to another disaster in another combination (and that includes dealing with human errors). People without the quality mindset often decide that it's enough to fix ANY of the causes, because that'll avoid a repetition of the disaster.
Heartbleed bug accused charged by RCMP after SIN breach
Cistern and Sieve: How YC, Peter Thiel and General Assembly can change education
I disagree with the entire 'very little cause required to compel disclosure of metadata'; essentially, the third-party doctrine should only apply if users are consciously giving their data to a third party for the purpose of redistribution, and not purely incidentally to a service.

If they can argue something like a copyright banner in a ROM is "a mere instrumentality", there's no reason the defense side shouldn't be able to argue giving calling information to a cell provider, or mail headers to a mail server, aren't essentially the same instrumentalities.

(I've talked to lawyers who agree, but they all also agree this ship has sailed for many decades.)

That said, yes, he's both technically and legally incompetent. It's sad, and has made bad law for everyone else.
The true value of an estimate is not about what you thought the project would initially cost, but rather, the true value of an estimate is as a tool to estimate the final cost of the project once the project is underway.

Trying not to get into too much detail here, but, when you devise your initial estimate you should have a list of deliverables and you should determine what you think those deliverables will cost to implement. Your initial estimate will then become your baseline, and is mainly used to keep track of what you initially agreed upon (scope) and as a way to measure your progress.

Imagine that based upon your original estimate you have a deliverable that to implement will cost $50,000, but you have already spent $30,000 to implement it and are only 10% done. Well then your new estimate would now balloon out to $300,000 and it will take 10x as long. If you replicate this process out across all of your deliverables based on their progress you will have a new estimate, as the project continues your estimate will become more and more accurate.

Beyond having a better understanding of what your project will actually cost, you will also have a tool to handle scope changes by management and/or the client. You will automatically have an idea of based upon your prior performance on this project the feature that they ask will cost them $X additional dollars and increase the duration of the project by Y Days, or, as a way to negotiate a reduction in scope in order to stay within your budget.

There are certain mega engineering firms that make all their money solely off of defining the estimate and scope at a very detailed level up front and then renegotiating the (hell out of the) price as new scope is introduced.

Here's a link for more information:

http://en.wikipedia.org/wiki/Earned_value_management
Do you have any non competes or IP agreements with Intuit / Turbotax that could be potential liabilities down the road?
Take a look at go QML. I think it'll be the one GUI library to really take off, if for no other reason than the guy working on it (Gustavo), is pretty brilliant, and it's going to be used to write applications for Ubuntu Touch.
It's amazing how following good coding standards can make bugs go away. If anyone disagrees, I would suggest reading Joel Spolsky's article "Making Wrong Code Look Wrong": http://www.joelonsoftware.com/articles/Wrong.html
That article changed my perspective on coding standards.

To your PSA, I would like to add: Never use the '!' operator at the beginning of a conditional. It's too easy to miss when reviewing or changing code, especially next to certain characters:

if(!llama) {
...
}

This is a tiny bit more text, and so much safer for maintainers:

if(llama == false) {
...
}
Is China's Biggest App Store Promoting Piracy?
The point made about "bias towards merging" is my favorite. It's hard enough to get people to contribute without compounding the problem by kicking back their work over minutiae.
It should be noted that this might not have been a coder error, but a merge conflict. Nobody should be reprimanded in that case, since it's nobody's fault (except whoever decided to not test or lint this file, but he should have been punished for negligence even if it hadn't caused a bug.)
Eiffel's contracts are really compelling, I wish there was a reasonable, non-hacky way to implement them in more mainstream languages.
Pneumatic Logic
Thank you so much for this! Awesome little sim/game. Beyond my coding skills, but it would be lovely to also show some of the Lagrange points for the orbits. I've noticed (I believe) that I can get objects stable around L4/L5 (but not L3) But I may also be imagining things :-) Very cool!
It's worth taking to heart. It seems to have come out of Heroku-land, and it's baked into Heroku. Of course, that's an even more restrictive environment in some ways, but the underlying concepts are true for larger and more complex things than can be easily executed in Heroku.

Now all you have to do is get them to grok immutability...
Problem is that you can DOS the system this way. You do not want to incent the defense to make weak arguments so that they can try again with stronger arguments in the case of a mistrial.
Quite ridiculous how you can get in court for sending bytes to a server.
Referring to Manhattan as 'the city' is very common:
http://gothamist.com/2012/05/21/do_you_refer_to_manhattan_as...
Whether it's capitalized is just a matter of taste, as seen in the comments.
Are you making the claim that language design has no effect on the number of bugs? That JSLint (for example) doesn't really reduce the number of bugs? If you're not saying that, then presumably JSLint / language design does reduce bugs, which is probably the main claim the article.

Nobody is saying that enforcing {} syntax etc. removes all, or even most bugs, but it removes a non-trivial amount of bugs while not making code particularly harder to read imo.
>A small latte usually runs around $3 or so. An espresso might be $2.25-2.50.

I don't live in NYC and lattes are more like $4-$5 here.
Campaign Monitor Raises $250 Million
> I think the most readable code has no shortcuts and no tricks. I'll take unambiguous over concise or 'beautiful' any day.

Ambiguity and conciseness are orthogonal concepts. Mathematics and formal proofs are very unambiguous, yet they are concise. On the other hand assembly code is unambiguous yet very verbose. Code has to convey two things:

1. "what should be done" to humans

2. "how to do it" to machines

Striking a balance between these two is difficult since it depends on each individual coder and the programming language. That's why there are so many syntax bike shedding wars because what's readable to one isn't necessarily readable to another.
You don't allow naked braces either. They have to be tied to control flow.
Yup, they'll be posted for download by anyone.
"I have just met you and I love you" [web APIs]
Michael Lewis said somewhere (I think the intro to The Big Short) that he never expected to write another Wall Street book after Liar's Poker. He thought it was the be-all, end-all warning to IB wanna-bees.

But he kept getting letters from college students to the effect of "I read your book, where is that kind of opportunity now?"

It wasn't just the money, or the power, it's just being more whatever than anybody else...
Well, TLS-auth should be used _on top_ of a PKI. It is a HMAC key that an attacker would need to know before he'd even be able to initiate a TLS handshake.

Thus, if you have used it in your OpenVPN setup, and if you know that the few users who have access to your VPN wouldn't have heartbleed-attacked you, then yes, you could assume that your private key has been safe from heartbleed despite an exploitable OpenSSL library.
Ask HN: How do you build landing pages quickly
Hi guys,
I am building a landing page for one of my ideas but I am doing it by actually coding html/jquery etc.
Is there a better way to build landing pages more quickly?
I think the '!' is easy to spot when using a good monospaced font.
It's optional though, and leaves too much room for ambiguity IMO, which I find annoying since the point of significant white-space is maintaining consistency.

These are all equivalent:

main = do
something

main =
do
something

main =
do something

And obviously, you can also not use `do` notation.
Agreed. GTD can be combined with this though (if you just ignore most of his post and focus on the "Three things of the day" point). ZTD calls these three things for MITs (Most Important Tasks) -- http://zenhabits.net/ztd-habit-3-plan/
Coding the Angular Tutorial App in Backbone
RCMP charge Ontario teen over CRA Heartbleed hack
Get them to read the right stuff. If they actually take the time to go through the canon of modern PM work (starting with Lean Startup), they'll probably start seeing sense.

As a formerly non-technical person, it's worth pointing out that it's really hard to understand the pain of development if you don't do it. So communicate the tradeoffs: that, they'll get. Say "I don't know" more, and be clear about risks in developing new features. Be open. If they're good managers, they'll respond well, assuming they trust you and not just their own genius (which I think is the danger with Idea Men).
I absolutely believe that languages matter and are the best hope for improving code quality and productivity overall. We need better languages.

But the way we get there is not to pick some small but critical bug that could be avoided by an arbitrary style change and declare that a language which does not suffer that stylistic pitfall is superior. The new language may have much worse flaws. You're just playing language flaw whack-a-mole at that point.

If we want to improve we have to get a sense of what types of bugs are most common across all programs and reason from a logical standpoint about how they may be prevented. This will solve orders of magnitude more problems than fiddling around with the syntax to minimize the number of typos people make.
You can track browser's ES6 support here: http://kangax.github.io/es5-compat-table/es6

The site's maintainer, kangax, on Firefox's recent ES6 work: https://twitter.com/kangax/status/456219547968614400

Jeez, @Mozilla adding ES6 features faster
than I can update compat table #firstworldproblems
Impressive feat. Took a few snaps on my Nexus 4 and it seems to work really well given a decent scene.
Can you provide a source for the NSA cracking tor?
It's not a silencing tactic, good lord, stop suspecting people have hidden agendas about trivial garbage like this.

Like the blog author, stop attempting to control what people say. Someone saying "I'm a product guy" is in no way a slight or a problem in the world. "I'm a product expert." There, solved.
I've not looked at the actual protocol, but it's not impossible.

If we assume every packet contains the client's (random, generated at process start) public key then the server could (in theory) perform key-agreement for every packet, decrypt it and handle it. In practice, it would cache the result so that it only does one key-agreement operation per client.

If the server crashes (did you have the server in mind when you said "other side"?) then it looses its cache, but the first packet that the new instance of the server sees will have the client's public key in it so it just refills its cache immediately.
Car UX
What types of roles are you looking for?
So can when.js which has become my favorite promises library:

https://github.com/cujojs/when

http://know.cujojs.com/tutorials/async/mastering-async-error...
A previous text analysis had identified the same person (as well as a number of converging clues):

http://likeinamirror.wordpress.com/2014/03/11/occams-razor-w...

http://likeinamirror.wordpress.com/2013/12/01/satoshi-nakamo...
Lack of proper training aside, from their perspective this sadly is the most rational thing to do.

Phone sales people are incentivized by management to minimize returns, because returns consume lots of time and money.

If you are a sales person, you know Windows Phones have higher return rates (because there will be some app missing or some other feature hole in WP). Selling it is risky.

An iPhone or a Samsung sells itself. And more importantly, it doesn't return itself nearly as often.

I like Windows Phone, but if I worked in phone sales I'd push people towards iPhones and Androids as well.
Well, personally I don't like whitespace significance... But then, I wonder if forbidding spaces* at the beginning of the lines wouldn't correct all the problems.

* Yes, mandatory tabs. I know lots and lots of people will disagree, those lots and lots of people are wrong. Spaces are ambiguous, and have different semantics on different context. In a flexible language that does not make much difference, but when you want whitespace to have a specific meaning, it does.
I think it's deliberately misleading to say the study is "from Princeton and Northwestern Universities," when it's a coauthored article by one professor from each place. I think that was done to make the study sound more important, probably because the author of the news article agrees with the premise of the study.
First reaction: Qt's inventor was in jail? :)
The keyboard is the module I want.

I used my T-Mobile G2 until it died a month ago, and had to do an emergency replacement, which ended up being a Nexus 5. I'm going absolutely insane not being able to just type without thinking about it. When you have to think about your input and often correct it, you are no longer able to simply stream your thoughts, and each micro-interruption is actually quite a distraction from getting things done. It's frustrating.
This is old news in the Bitcoin community... but it's far from definitive proof.
There's no reason to throw away crutches. Hell, I already implement his "three things" method. The only difference is afterwards I actually write down the three things so that I stay on target all day.
So I know this article is BS whining for two reasons:

0. Someone I met acquired the charter of a failing Midwestern local regional bank in order to save a ton of cash on moving funds into the us. This person was under 30 at the time. And it was tax and banking legal considering the law firm.

1. Defensibility of a business model is your friend, not you enemy. Look to how incumbents do it. What can you improve on? Just remember that the harder it is for you the harder it is for everyone else. If it were easy, everyone would do it and the competition would be even more cutthroat elsewhere (patents, distribution, connections, etc.).

To potential investors they probably signaled lack of hustle to find creative solutions to get past their current and all other future dilemmas. Without an unique, defensible, competitive advantage there's really no for an investor to throw down on a venture.
(OT)
I am given the idea that popping up a banner soliciting an address for e-mail updates (as this site does) is a standard practice on many blogging platforms, and that it is apparently quite effective at retaining users, but as a user I find it quite obnoxious. I opened this page in a new tab, and when I clicked over to it I did not immediately recall what the page was about. The 'close' button is also small and hard to see.

I purposely avoid subscribing to e-mail updates because I get very little to nothing out of them that I could not also get elsewhere, e.g. through an RSS reader, at my own convenience or intent. E-mail updates almost always read to me as advertisement, similar to dead tree junk mail.

Compounding this annoyance, though this is squarely in the realm of my own responsibility, I configure my browsers to clear cookies every user session. So doing allows me to easily be logged out of services simply by closing my browser and has the side benefit of perhaps confounding tracking services just a little bit. Unfortunately it also means that any of these websites which I visit very rarely will display the subscription pop-up every time.
At the least, a writing style analysis is stronger evidence than the last pile of shaky not-even-coincidences used to point the finger at someone.

I'm far more likely to believe Satoshi is Szabo--or a collaborative group that includes Szabo--than someone who is not actually a recognized expert in cryptography.
The pixel is very similar to a Macbook Air, (IIRC, thiner/lighter) except has a HD-touch screen. If they refreshed the processor, all that would be missing is a decent harddrive.
I find this stuff really interesting! I'm curious though, how much is Agda suited to prototyping and the like? Do all of these layers of proofs and definitions build up a foundation which eventually allows you to program "like normal", or does pretty much everything come down to writing a ton of proofs, which seems like it would be academically interesting but burdensome for real-world applications? Does Agda encourage modularity and abstraction as much as Haskell does? More so?

Also does Agda have any support for mutation? How does it deal with IO?
Multicellular Economics and the Mechanization of Cooperation
Now you have the bug occur if someone forgets an equal since this is always true:

if (llama = false)

So use Yoda conditionals instead:

if (false == llama)

Is that really an improvement over the original? As I've stated in my sibling reply, you are decreasing human readability for machine readability.
3-d printed outhouse. boom, problem solved
"A group of 40 students and researchers at the university studied the writing of 11 candidates...It’s important to stress that the team isn’t saying its study points conclusively to Mr. Szabo, only that of the people it studied, he appears – on the basis of his writing – to be the most likely candidate."
- They only compared people they already suspected.

- Satoshi should've already known about linguistic analysis.

- It's likely Satoshi had someone read and rewrite his works to avoid linguistic analysis. Nick Szabo would've been a logical choice for this.
"My pet language renders that problem impossible."

Um... OK.

"Therefore you should use my pet language rather than one written in 1968 for a PDP-11."

Not so fast.

First, when the language was written has nothing whatsoever to do with how useful it is today. (Cue the Lisp advocates.) It's just a gratuitous slam, and it comes off as being petty.

Second, even if Eiffel does completely prevent this class of problem, what about the reverse situation? What classes of problems does Eiffel allow that other languages prevent? (Don't bother claiming "None". That's not realistic. It just means that either you don't see the flaws, or you're a propagandist.)

It's about the best tool for the job. Now, it's fine to argue that another tool would have been better for that particular job, but "avoiding one particular class of bug" is nowhere near good enough.

One point for the original article, though: Code does matter. Choice of programming language matters. Code reviews matter. Testing matters. Code review policies matter. Develop training matters. Developer culture matters. It all matters.
it tab completes more than bash does. switches, parameters, servers defined in your .ssh/config file etc. it's really impressive. coupled with the jump/mark script[1] it's amazing.

mark . marks the current directory in a folder full of symlinks.

jump <tab> expands to a list of your favorite folders.

super simple and extremely low overhead.

[1] http://jeroenjanssens.com/2013/08/16/quickly-navigate-your-f...
If I wrote a book on brain surgery, the critics would be much more useful than the author.
What about tor nodes makes them more likely to be running older versions of openssl than webservers?
Go has been very stable for quite some time now. There is a backwards compatibility guarantee while it stays in 1.x. Your old code will still build with new versions of Go. As for optimization, yes, it will get faster and better... I don't see why that's a drawback?

I don't really know what you mean by "big industry". Canonical's Juju is written in Go. Docker is written in Go. Iron.io is written in Go. Cloudflare and Youtube use Go.

Lots of companies use Go.

CodeIgniter and Laravel are web frameworks (which happen to be written in PHP). That's not even a valid comparison to Go, which is a programming language.
Of course, in programming in the first case, "b" and "d" both happen when "a" and "c" are both true in many languages, unless "b" is something like "return e"

But, anyway, I was mostly joking -- its not like your meaning was at all unclear.
If you're using a language more complex than HQ9+ to accomplish your goal, there will always be a Wrong Way to do something and someone is going to find it. Granted, you can attempt to limit the number of Wrong Ways, but it will never be possible to eliminate them.
WordPress 3.9, "Smith"
Here’s What Drone Attacks in America Would Look Like
I am surprised I have not seen anyone mention this yet but a simple regression with line coverage enabled would have caught this. Is it not common in the software community (I do mainly Hardware) to run regularly with line coverage? This seems like a basic problem with process in my opinion.
Two consecutive gotos wouldn't cause a bug if the indentation mattered, it would just be unreachable code.

The programmer is already communicating intention with code style (scope), you might as well design the language to use this signal.
Does Agda provide tools for program extraction? I'm curious where the state of the art is for using proof checkers/dependently typed programming languages to derive correct-by-construction programs in lower-level languages like C.