2,193 karma · joined July 1, 2010
This slow realization made me give up calling people out on calling themselves hackers. It used to be that a hacker was someone who was particularly adept at finding clever ways to misuse, change or exploit something. http://hacks.mit.edu/ and http://www.catb.org/~esr/faqs/hacker-howto.html were the canonical references. Hacks were contrasted with engineering -- both constructive creative output, but one involved detailed in-the-field knowledge while the other was a more principled approach. 'Street smarts' vs 'book smarts' if you will. Both were needed for a successful enterprise. Calling oneself a hacker was equivalent to giving yourself a nickname -- socially awkward and decreasing the likelihood the moniker would stick.
Now 'hacking' is synonymous with prototyping, or even more esoteric types of development (what the hell is 'hacking education' supposed to mean?). This isn't entirely untrue as quick prototypes often contain "awful, we shouldn't be doing this" kinds of code. However, they do tend to lack the righteous "awful, we shouldn't be doing this but damn is that awesome" code tradition calls for.
Like you said, definitions change and the only thing that matters is if your idea is communicated; ultimately you have to go with the flow...
Make sure to look at https://github.com/charliesome/Fructose/pull/9/files for full effect.
I certainly understand your position on this, but I want to point out something interesting: your hesitance to speak because you might say "the wrong thing" actually has an effect in itself. Nobody wants to make other people feel uncomfortable. If you're a woman and entering a room makes people worried about "saying the wrong thing," then you feel bad... reinforcing the impression that a woman somehow "shouldn't be there."
It's awful because a well-meaning person ends up preserving the situation they're actively trying to prevent.
You claim that there isn't much of an upside to a guy speaking in this situation -- there is in fact a quite large upside. By taking place in a conversation like this, you're sending a social signal that this kind of behavior -- talking about these issues in the open -- is encouraged and normal. It sounds like you're worried that this will backfire, but I can tell you from experience that it doesn't when handled correctly. The basic rule to pull this off is to stop seeing certain classes of people as 'others.' It's harder to do than it sounds, because you'll find that lots of your cognition has this stuff hardwired. Eventually you'll recognize when you're thinking this way and take corrective action.
s/females/people/. This yields the same result.
> Can we start to gripe about why there aren't more men in the fashion industry?
You've never met anyone from NYU, have you?
http://www.google.com/gwt/x?q=hacker+news&ei=d6xmT8nQB4S...
Note that I had to specifically choose "mobile view" to get this.
I highly recommend you take a look at PNaCl: portable LLVM binaries run in the NaCl sandbox. Since LLVM bitcode can be JITed (or even offline compiled before execution), you would be looking at optimized code for whichever target you're running on. Very exciting stuff.
http://www.chromium.org/nativeclient/pnacl/building-and-test...
HN is focused primarily on business. A PHP photo sharing site has a much lower effort-to-bux ratio than some wacky electrical switch. This is completely fine, but you have to make the separation between "dollas" and "innovation." Often they live under the same roof, but one doesn't automatically imply the other. Ideas are where researchers play, and researchers are the antithesis of business.
Your advice ('think less, do more') still stands. I just want to let you know that ideas do have merit, you just have to look in the right place. Good luck!
[1] http://www.facebook.com [2] http://www.google.com [3] http://en.wikipedia.org/wiki/Transistor
This keeps getting thrown around but I'm having a hard time identifying a good source (other than a bunch of blogs repeating the same 'fact'). The best I can do is this set of slides which claim 'a 2.1x improvement' [1], but no confirmation that it's actually in use.
The brain is very poorly understood, and throwing random electrical fields across it "because I saw it on extremetech" is a terrible idea.
No. I'm arguing this: take a 44.1kHz signal and upsample it to 192. It's the same signal, same bandwidth and everything. Duplicate the stream and add a 1 sample delay to one of the channels. When you hit play, that delay would be there. If you downsampled the 44.1kHz signals after applying the delay to one of the channels, you would almost hear the same thing. The difference is that you could not detect the difference between the signals until after a few samples. With the 192kHz stream it would be unambiguous after 2.
Remember, Nyquist-Shannon holds if you have an infinite number of samples. If your ears could look into the future then what you say is perfectly correct, but they need time to collect enough samples to identify any timing discrepancies.
This is true, but different than what I am arguing. You're saying that a listener over time will be able to tell that the two signals differ. I am saying that a listener will be able to determine this at fractional wavelengths.
It's similar to dithering a high dynamic range signal onto a lower bit depth: more than two samples are required for "evidence" of two different signals, while sampling at a high enough rate will tell you this almost instantly.
Again, I don't know if human ears are able to detect this, just that I haven't seen it addressed in these discussions.
1) Any well-designed system is going to have headroom. Period. Just because 48kHz can capture the frequencies the human hear theoretically, it's always good to have a little wiggle room. This comes into play even more with interactive situations: humans are particularly sensitive to jitter. Having an "overkill" sample rate lets you seamlessly sync things easier without anyone noticing.
2) 192kHz comes with an additional benefit besides higher frequencies: it also means more granular timing for the start and stop of transients. More accurate reverb would be the obvious example. I don't know if the human ear can discern the difference between 0.03ms and 0.005ms but it's something I don't see mentioned often.
Not to throw more feature work on you guys, but I always thought it would be neat to have an IRC client email you if someone mentions you while you were away...
I've been using 280s at work for a few weeks now and I'm not really digging them. At home I have Shure SRH-440s, but replaced the stock pads with pads from the 840s (about $20 off amazon). They're monitor headphones so the response is meant to be flatter; the net result is notably quieter bass that sounds more "present" than pounding your ears. At first I disliked it but once you start listening for a bit you grow to appreciate it.
* Strange nested query rules
* Language encourages Cartesian products for virtually every non-trivial calculation. This makes join order crucial for reasoning about performance.
* Humans don't have the brain capacity to reason about these joins, forcing the logic onto the query planner.
* Humans don't have the brain capacity to reason about the query planner reasoning about the joins.
* End result: bizarro-english syntax that's supremely hacked-up to twerk the query planner to do your bidding.
"the most effective music to aid prolonged periods of intense concentration tends to have a mixture of the following qualities:" is too clinical to describe something as personal and emotional as music...
Actually, this is likely an improvement on rateless/fountain codes. A key feature of these codes is the ability to reconstruct an entire message block if you collect "enough" subcodes, regardless of order. These actually obviate the need for retransmission and are crucial for things like reliable multicast wireless: it would be a nightmare to keep track of each of your receivers and retransmit lost packets to each one, with rateless codes you theoretically don't even need to know your receivers are there. Just keep spewing out data and eventually they will receive enough to make up for missing blocks.
A casual glance at this paper implies that they've found a model of these codes that takes into account standard models of noisy wireless channels; using this model allows you to optimize your code to have less error correcting overhead (meaning you need to collect fewer packets to successfully reconstruct the original message).
More info, and perhaps a more coherent explanation: http://en.wikipedia.org/wiki/Fountain_code