Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Jabbles
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
73 ms
·
751.
▲
by
Jabbles
12y ago
That assertion that you can win more than half the time at "guess the higher number" sounded weird, but testable. http://play.golang.org/p/E1L9spOjBk Cool.
752.
▲
by
Jabbles
12y ago
Sounds like we agree then :) If we assume that no (Csmith) bug will be fixed without a reduced test-case, then the choice of which one to use as a regression test is obvious.
753.
▲
by
Jabbles
12y ago
I disagree that the tests are not obviously worth keeping. Having a large suite of regression tests is vital to stop bugs reappearing. This type of research spawns other research and projects outside of academia by acting as a proof of conc
754.
▲
by
Jabbles
12y ago
In comparison, the Go standard sort function is not vulnerable to this, and references the same paper as this article: http://golang.org/src/pkg/sort/sort.go#L168
755.
▲
by
Jabbles
12y ago
Does anyone know the total number of lines of Go on Github? Without knowing that this number is meaningless.
756.
▲
by
Jabbles
12y ago
Another article on CrossFit, written by Mark Rippetoe, a famous and influential strength coach, is here: http://www.t-nation.com/training/crossfit-the-good-bad-and-t... He makes many of the same points, but I find the
757.
▲
by
Jabbles
13y ago
https://www.google.com/dashboard
758.
▲
by
Jabbles
13y ago
As much as I want to emphasize that this is not the right way to think about programming in Go, I do want to point out that the example has a lot of extra code that isn't needed. Indeed, it's not really possible to have a bug of
759.
▲
by
Jabbles
13y ago
A critical response by Benny Lewis: http://www.fluentin3months.com/chinese/
760.
▲
by
Jabbles
13y ago
So? I mean it's probably nice to have, but the performance of Redis isn't important enough to be a factor in the scalability of this. I just tested a binary search of 8 million random 100 byte DNA strings written in Go. 10,000 req
761.
▲
by
Jabbles
13y ago
Is having a beard something that all programmers should strive for? Or just the men?
762.
▲
by
Jabbles
13y ago
It's unfortunate that it was too big for an HN comment, which would probably have prevented it being posted again as a topic. People who are genuinely interested in the book could have searched HN and found the original review. This th
763.
▲
by
Jabbles
13y ago
I can't comment on the author's cryptographic knowledge, but his Go seems non-idiomatic, and in some cases plain weird. For example, this function stores the length of a slice in a variable, creates a new slice of the same length,
764.
▲
by
Jabbles
13y ago
Note the use of receive-only channels: func merge(cs ...<-chan int) <-chan int { Inside the function you cannot send to a member of cs - it will give you a compile-error. Outside the function you cannot send to its return val
765.
▲
by
Jabbles
13y ago
e.g. sync.Once() instead of init() unhelpful named return parameters didn't use range over channels
766.
▲
by
Jabbles
13y ago
Use bcrypt. http://godoc.org/code.google.com/p/go.crypto/bcrypt
767.
▲
by
Jabbles
13y ago
How hard did the family actually try to solve this mystery though? https://www.google.co.uk/search?q=OFWAIHHBTN
768.
▲
by
Jabbles
13y ago
I dislike this line of reasoning. If you add up the effects over many people then obviously you get a large number of minutes that were wasted, but those people collectively had many minutes to waste. You cannot claim that those minutes cou
769.
▲
by
Jabbles
13y ago
Indeed. Go is awesome, but this article is not. If you seek to learn more about Go, try http://tour.golang.org/#1
770.
▲
by
Jabbles
13y ago
Ah, I see - wow. Things make more sense. Thanks.
771.
▲
by
Jabbles
13y ago
Given that I know very little about Krout, perhaps you could explain why you participated in the first place. I don't wish to sound rude; I'm genuinely interested in what exactly you did, and why you thought it was worth doing. Ba
772.
▲
by
Jabbles
13y ago
http://imgur.com/vn27Bf6 This does sound like a bait-and-switch from Klout, but I don't understand the appeal of networking for networking's sake.
773.
▲
by
Jabbles
13y ago
Algorithms aren't really about recognising standard implementations - although in preparation you'll certainly learn that. It's about having a deep understanding of programs' flow, and being able to recreate and combine
774.
▲
by
Jabbles
13y ago
Tell us what you think is missing. You don't "feel nearly prepared". Have you prepared? These interviews (for better or worse) tend to be algorithm based. How are you on those?
775.
▲
by
Jabbles
13y ago
I'm suprised. I thought it was a joke: https://news.ycombinator.com/item?id=5148895
776.
▲
by
Jabbles
13y ago
What could Google have done better? (Specifically in regards to this case. And assuming they pushed back on orders like this, like they claim to do.)
777.
▲
by
Jabbles
13y ago
Google "mobile trends"... result number 4...
778.
▲
by
Jabbles
13y ago
I don't understand people's problem with estimating. It's a useful skill. Perhaps it would be better if the questions actually related to technology, rather than golf balls - but the principle is the same. For instance - &quo
779.
▲
by
Jabbles
13y ago
If he failed to show up for work, officers would be sent out of concern for his wellbeing. The whole point of banning him from leaving the country is to try to prevent him "defecting". Waiting for him to come back is pointless. He
780.
▲
by
Jabbles
13y ago
Well that's embarrassing... Still, why aren't airports checking if people specifically banned from flying are trying to fly?
More ›