ogreyonder
https://news.ycombinator.com/item?id=6660089
http://i.imgur.com/mmPAztu.png
I didn't get much interest so I didn't bother building it :)
However, it's still a VERY good idea to do if you plan on holding stock.
I know stories of several people who were exercised options on 7 figures of stock, only to see the price collapse before they were able to sell. The taxes they owed because of that eclipsed their net worth several times over.
I'd argue that if you can't meet deadlines with scrum, there's no way you'd meet them without it. His definition of 'shippable' is very narrow--like you said, just because it doesn't meet console certifications doesn't mean that it's not "doing scrum".
I wouldn't put the app I've got after the first dev sprint on the app store, either. It's not done.
Just apply the usual headline rule: If the title is a question, the answer is "No."
You'd think they'd have at least one guy dedicated to nothing but breaking their software. They make my salary every day with transaction fees (well, maybe until recently) so you can't say they're unable to afford it.
Edit: Rereading this, it sounds more accusatory than I intended. I think your clarification was perfect, but at the same time that MtGox is at fault.
> Just ask. The worst they can say is "No."
And that's where I have to ask: what do you do when they say no? I followed this advice a year back or so and it essentially put the brakes on any serious side-projects. I work for a big company that you've absolutely heard of.
To the coders: Nice job on using multiple URLs to allow pages to be viewed without JS enabled. Having to reload each page when it is requested is not trendy, but it's nice to know Mailpile will work on locked-down browsers. Kudos!
In brief: the only source I can find (that page) just contains a few sloppy lines of pseudocode. Where is real description and proof of its properties?
You sound knowledgeable, so perhaps you could clean up their algorithm for me? There are a number of problems with their description that make it hard for me to evaluate. Having tried designing a memory-hard algorithm, I'd like to see what their key insight was, but there are a number of problems with their article. They use confusing operators, the wrong terms, and seemingly random constants.
How did they come up with the numbers 2, 3, 11, 2^21, and 2^22, for example? Is D the hash function or the underlying data? Or is 'data' the underlying data? Does + mean addition or string concatenation? What about "++"? They never even use "||", which they defined as string concatenation... Where does the nonce N come in? Is that actually supposed to be 'n'? How do they justify that the optimal algorithm is the naive one? There is essentially no proof of this claim in the article.
In short, I'm very suspicious of their "memory-hard" algorithm. It took a fairly dense, multi-page whitepaper to explain Scrypt, and yet their 'superior' version is just a couple of sloppy lines of pseudocode with no justification.
Here is what they wrote, for reference:
Let D be the underlying data (eg. in Bitcoin's case the block header), N be the nonce and || be the string concatenation operator (ie. 'foo' || 'bar' == 'foobar') . The entire code for the algorithm is as follows:
0: D(data,xn,0) = sha3(data)
1: D(data,xn,n) =
2: with v = sha3(data + xn + n)
3: L = 2 if n < 2^21 else 11 if n < 2^22 else 3
4: a[k] = floor(v/n^k) mod n for 0 <= k < 2
5: a[k] = floor(v/n^k) mod 2^22 for 2 <= k < L
6: sha3(v ++ D(data,xn,a[0]) ++ D(data,xn,a[1]) ++ ... ++ D(data,xn,a[L-1]))
The article abuses the word "derp" to sound hip, makes weak shots at people and ideas left and right (without ever arriving at an argument), and generally rambles on for a whole page.
What a waste, how did this make HN top 20?
Your bank offers the illusion of privacy. Sure, a random person can't just walk up and see your balance. But a teller can pull up your account and look around. Sysadmins can certainly see your money pop up in server logs. A particularly motivated individual might even be able to pull data from disk images or memory if they were so inclined, so how safe is that information really?
I'd argue that knowing everything is public is better. It motivates people to come up with solutions like Zerocoin and CoinJoin.
Nope, National Reconnaissance Office.
http://en.wikipedia.org/wiki/List_of_NRO_Launches
I mean, at least they're being honest!
"UC Berkeley scientists have developed a system to capture visual activity in human brains and reconstruct it as digital video clips..."
http://gizmodo.com/5843117/scientists-reconstruct-video-clip...
I would like a historical example demonstrating the problem of the gold standard. The world worked this way for centuries, so surely there must be some documented case of one of the doom scenarios you proposed.
I've heard this assertion a lot in regards to bitcoin/deflation. However, everything I can find winds up in the same place. The gold standard was fine, but countries abandoned it so they could print endless money to fund World War I.
That is entirely the point. He may well have been willing to do "the time". But "the time" is wildly disproportionate to "the crime". This is bad for the same reason that we don't execute everyone convicted of breaking the law.
Furthermore, how does your logic apply to the NSA? A group of someones very clearly broke the law hundreds of millions of times after being told to stop and being kicked off networks, then finding ever-more invasive ways of stealing our emails to grandma. Remind me, who is threatened with jail for the next billion (!) years under the CFAA?