Like many things, Chomsky is both right and wrong. He's right in that if we studied the structure and functioning of the brain we could built more accurate AI. He's terribly wrong because the structures of the brain are fuzzy and give rise to probabilistic and 'statistical' functioning that is itself based on training (much like the models he derides).
Even your own blog posts says that you basically just followed the getting started guide for ruby. Personally, I would not use an untested, brand new to me, technology on anything that 'had to work'. And if this wasn't that important, then chalk it up to a learning experience. MongoDB's decisions might not fit your personal style, but your attitude towards learning is a poor model for technology.
Do my bitcoins stay as my bitcoins OR do I transfer my coins to coinbase and when I want to use them you transfer the same value back? I would feel a lot more comfortable with the later where your company was liable if you got hacked.
There's a huge difference between privacy and secrecy. Any debate about this topic that does not immediately make that distinction is futile. I don't keep secrets from my wife, but I still close the door when I use the washroom.
This is dumb for one simple reason, It divides candidates based on an arbitrary line that has only limited correlation to the desired split: Those who fit your job requirements vs. those who do not. Instead, ask them to solve a pertinent problem to your company. If they go down the wrong path, give them a hint as to the right track and see how well they can grasp the new method. Simple. OR even better ask the candidate to explain how they solved their own last 'interesting' problem.
How can he write such an article, stating that he used C# because he knows it, and not tackle the problem using the main resource for such issues in C# / Java: Interfaces. Using interfaces, you can decouple all of those classes from each other, and never have this issue in the first place. If the stated model is the way he would typically tackle a problem in C# then there are fundamental issues with his choices, something that is not a failing of the Type system.
The benefits of writing your own package is that you can post it on HN as a 'news' article and have thousands of potential employers look at it without applying to any specific jobs... :)
The only time your actual hourly value matches your potential hourly value is when 1) You have significant funding, 2) You have a time-to-market deadline, 3) You have either an income model OR a continued funding potential based on point 2. If you have all of these things, then a day trip to save $600 bucks is a waste, otherwise saving $600 dollar today gives you $600 more for tomorrow. This blog entry is naive.
From my understanding of this, HFT basically makes it impossible for a non-HFT trader to buy at anything but his maximum buying price and to sell at anything but his lowest selling price. This seems like it would significantly undermine the profitability of the market for non-HFT traders.
Amazing that almost zero thought on the side of aerodynamics and engineering went into the production of such a high-amount-of-work project. The second the 3-foot tie points are removed, the center of mass of the driver will cause it to flip upside down instantly.
Or, you know, you could just use the electricity to convert water to hydrogen (itself a usable fuel). How much of the energy required for this reaction is actually coming from the carbon / atmosphere? I would guess very little.
The majority of AECL (the CANDU reactor team) is un- or under employed after the buyout from the Canadian government - that's an entire workforce to tap into.
They haven't actually changes the lambda code at all, they have only changed the fact that previously the foreach variable was declared outside the loop, now it is declared inside the scope. The lambda still closes over the loop variable. If you code your own loop, feel free to declare the loop entities anywhere you like.
I have never used Haiku myself, but that is exactly what I was thinking while playing with this example. Did Haiku 'remember' the original size so that it bounced back as you dragged it away from the edge?
I think apple was smart with the way they went mobile, in that they didn't really try to carry over any of their exiting OSX UI. Often it is 10x harder to unlearn habits than to form new ones. If I'm presented with something that is 'exactly like before except for a bunch of glaring omissions and additions' it will feel like the uncanny valley and getting used to things will be much harder. Apple went for the 'Everything that you do in iOS is new but seamlessly intuitive' route which lends a reasonable learning curve and more importantly no steep 'unlearning' curve.
Are the measured effects of tDCS really large enough to outweigh any effects from confirmation bias and statistical anomalies? Were the tests performed double-blind using placebo units?