skysight-inc/HackerNews huggingface dataset:
The big, protruding heel of the human foot is completely counterproductive for running.

The heel does not protrude when running.

Humans have to consciously learn a proper technique for running to avoid misusing the heel. Doing "what comes naturally" is just horrible.

Children, when running, do not land on their heels. Heel-landing is a learned development caused by heel-heavy shoes. Children land on the front/middle of their feet.

By contrast, an animal doesn't have to study running technique. A cheetah doesn't have to think "Gee, I'm doing this wrong according to some pages I Googled; I should change my form so that my center of gravity is rather such and such, and my footstrike is altered in such and such a way."

Cheetahs do have to think about how to run. Have you ever seen cheetah cubs?

I should change my form so that my center of gravity is rather such and such, and my footstrike is altered in such and such a way."

Try running without shoes. You'll learn very quickly, without google, not to land on your heels. It's the same way that animals like cheetahs learn to run-by doing.

The sheer thickness of the meat and fat on the lower leg of a human tells you that we have evolved away from running. Running requires a stick-like lower appendage, with all the muscle higher up.

Every claim in that paragraph is wrong.
I've worked on one project with Pyramid extensively, and I've been relatively pleased. It gives you a lot of flexibility, which can be good and bad. There is useful code that helps you unit test your app, and it is not a particularly opinionated framework. That being said, the number of options that pyramids allows can be a little overwhelming -- it gets a grade 'C-" when held up to the zen of python's line: "There should be one-- and preferably only one --obvious way to do it." When held up to "Although practicality beats purity.", as well as most of the rest of the pythonic ideals, Pyramids gets a solid A.

Personally, I'm excited to explore flask more, since it seems to put the ball entirely in your court. I like the concept behind flask a lot -- for some projects I'm willing to sacrifice additional framework features in exchange for a more careful understanding of everything I am adding to my app.
That seems like the classic mistake of believing that the larger market assigns importance to repairability. I haven't seen much evidence this is true.
> The mental image of a huge ram sucking IDE with code completion for frameworks is simply incompatible with

> what I would consider the ideal creative process for me as programmer.

Java has long been my primary professional language, and over the past few years Go has taken on a strong secondary niche at my job. I'm big fan of both, and tend to play Switzerland in arguments between them.

That being said, the best Go IDE out there right now is the official Go plugin for IntelliJ... which again, happens to be the best Java IDE out there. If you are doing modern software development in ANY language, then you are probably traveling one of three paths:

(1) Using an IDE based on JetBrains or Eclipse.

(2) Using a variant of Microsoft Visual Studio, which is about an order of magnitude more bloated than #1.

(3) Using a plain text editor, which for a typesafe language is a bit daft.
Only if you've already used Inbox, correct? It's just a reminder to existing Inbox users. The reverse is not necessary since anyone using Inbox is already familiar with Gmail and using Inbox on purpose.
On the spot. I fully understand that many good engineers could freeze up, myself included. That is the reason the coding question is about a realistic problem. No dynamic programming, graph theory, suffix tree, etc. Also, before the coding, I would talk to the candidates about technologies listed in their resumes. It is mostly like a talk between two engineers in a meetup or a conference, not a technical test. My intention is to build an environment that the candidates can feel like real work environment as much as possible. It also helps to bring up the candidates spirits. We are talking about something we like!

As long as the candidates get the logic flow on the solution, can write code down in well-formatted manner, pay attention to corner cases, it doesn't matter if the candidates actually complete the coding, if I think given enough time in a real work environment that the candidate has no problem in doing it.

There are some red flags I pay attention to. For example, readable code is very important to me since we work in a team and we spend more time reading code than actually writing it. Once we had a candidate. he got the coding right, but his code was very hard to read. It reminded me of some obscure C code in the past that one statement was trying to do many things so that it became very convoluted. For me, it is not "smart". It is bad engineering.
I want to contribute to this but there are a few things holding me back.

- usage of global instead of commonjs or es6 modues - using an uncommon build system makes me uncomfortable

- _.can instead of prototype or just object creation - I cant say I understand why.

What I want to do

- allow it to use multiple renderers - toString, DOM, blessed with the goal of image output and webworker proof of concept

- give promise support to get Initial State - when attempting isomorphism in react, creating components based off a database is a pain unless retreived before hand and passed from parent to child in often disgustingly deep manners. Simply allowing the return of a promise fixes this in many ways
I do agree with your general point.

Your characterization ("Maybe some labs that wanted a unixy OS and, again, convinced their purchasing officer to buy a Mac Pro?") is a little off -- where I work, MBP's for laptop replenishments are treated exactly the same way as Windows systems, you just tick a different button on the order form.
I interpret this as: Page render latency probably degrades, but the site doesn't go down. Slower loads certainly have a monetary cost, making 11 machines worthwhile, but in a pinch at least they won't go fully offline if 10 die.
> The single most effective way that I've found to interview for "interest" is to just get them talking about something they've done before and ask them to go deep into the details. You get everything you need from watching somebody talk, with a smile on their face, about how they solved some problem in a creative way that makes them show some pride.

Sorry, but you are being scammed. You are selecting for sales skills, not technical skills. Read what you've written. You're judging someone based on how they presents themselves - not anything about technical ability.

I have interviewed many people who are great at doing this impassioned sales speech, but are terrible at actual engineering. And in fact, many good engineers are not good at selling themselves in this way - they have spent most of their lives deep in code, not working on their social skills like normal people.

Why not actually test them similar to what they're going to be doing? If it's a sales or advocate role at your tech consultancy, well then sure, your approach works.
This makes me think of that study[1] about doctors being away on conferences. I think it likely comes down to recognizing that experience rarely, if ever, trumps solid analytical thinking.

[1]http://archinte.jamanetwork.com/article.aspx?articleid=20389...
Just build yourself some simple mappers with hand written queries, and you've got better performing code than any ORM will ever give you. Honestly, the biggest problem I find with most webapps performance I've worked is on caused by terrible queries written by the ORM.
https://github.com/skelterjohn/wgo
"I don't like Oracle. I don't like the JVM."

You could just save yourself some (a bunch) of typing stopping there. All the other reason make you look like a clown.
Always a little disappointed when I remember ReactOS does not mean React.js OS.
> After their name showed up on that slide in the Prism leak without their cooperation (meaning they had been stepped around by the FBI. Some of the earlier companies had willingly volunteered data)

I know it's a bit off topic but I'm really curious about this - do you have a source that shows which companies willingly volunteered data and which were stepped around? I wasn't aware that anything like that had come out.
np. As was mentioned elsewhere in the thread, S is a pretty ancient language so R brings along some baggage with it :)
Its not one more Gadget that you have to carry around. New Lenovo Laptops and Samsung Phones already have UAF enabled Fingerprint Sensors that could be used for all your Web Authentification needs. The Yubikey is either the size of a USB slot or the size of a key on your keychain, so even your second factor is pretty minimal in size.

Alternative Login is always a problem, their is always a tradeoff between security and useability. You could easly print out some backup access codes. You can continue to use your E-Mail as a anker, you get an E-Mail and then your allowed to register a new token. That leaves the question of how does your E-Mail provider secure its login? I think Google is a good example of the options that are possible.
Depends on the usecase. I deal with java in the hadoop/big data space and I constantly wonder how much better the ecosystem would have been had it been implemented in a solid systems language.

I also find the tooling for go vastly superior out of the box compared to what i end up using with java/Scala. XML?! Wtf?!
> Are you referring to the "(100drive-failures)/(drive-hours/24/365)"? There's no multiplication of total # of drives and # of failures in there.

Perhaps the problem is the specific example given. 100 is the size of the drive fleet and also the multiplier required to convert to percentages. Let's assume you are right and the 100 in the equation is not #drives.

Even so, I find the approach questionable. If the point is calculate the proportion of failures then that (overly simplistic) calculation is:

[#failures] / [ #drives] = 5 / 100 = 5% failure rate.

But this isn't what's calculated. Instead the author calculates the proportion of drive-years per annum affected by failure. For the 100 drives in the example the cumulative number of operational hours given in 2015 is 750K hours (out of a possible 876K hours, had the drives been operating 100% of the time).

That's a problem because 750 / 876 = 85.6% of total time.

5 / 85.6 = 5.84% "failure rate" which seems to me an overstatement.

The problem gets worse as the number of operational hours decrease. Imagine for a moment the 100 drives only operated 50% of the time in 2015. We have:

100 (5 / ((875K*0.5) / 875K)) = 10% "failure rate". This despite only 5% of the drives having failed.

Wat?
> I come from PHP, where when you sneeze an ORM appears.

YMMD.
Beijing takes the cake for both craziest bus drivers and bicyclists, beating Hanoi and Davis, CA.
New European Digital Community
Thank you, I don't get it neither. The delusion in this thread is hard to believe.
Allowing sellers not to fill out additional information that they easily could provides a useful signal to buyers about how well the transaction is likely to go.
Ask HN: Best resource for learning some general UI?
Been working on a new site and I've hit a wall with the front-end. My JS/CSS/HTML skills are good enough but I lack the basic knowledge of how design works.

What are the best things to read to get a better understanding?

Site is https://new.soundshelter.net
Ok, I think you got the points right. I did not look up the details about this case properly in the first place.
I think you're missing my point... If rates go up, it doesn't help me that much as a buyer, because I can afford less house.
I think perhaps just to remove SQS as a bottleneck for benchmarking purposes?
You might be onto something there. I will pass that thought onto her, that a legal-focused software company may give her more of a look than others. Thanks for the idea
As others have said, it helps quickly orientate yourself before you start typing. It's hard to explain rationally but having that makes me much more productive.

I've been practicing by my work (as a programmer) and actively learning it aside -- typing without looking, and I am damn good at it.

There are however different use cases. Sometimes I have long reading sessions. Suddenly I decide the story is too big and want to stop reading it. Or I try to find a keyword in it. Or a hundred more things.

If I am to use programming terms, it reduces your bootstrap time when you want to use the keyboard after a period of inactivity.

...That, plus the fact that most are gorgeous and simply very nice to look at. There are definitely aesthetical factors as well, won't deny the facts. So it's 50% subjective, no doubt.
Bitnation launches Constitution with Ethereum
Apparently his enthusiasm remains high!
ReactOS has been around for a lot longer than React.js.

However... if there was a React.js OS, then I'd love to see ReactOS run on React.js OS. At that point, I'd love to see this run on ReactOS.
Don't forget the psychotherapist!
cannot create an account... Facebook Object ( [sharedSessionID:protected] => [appId:protected] => 255439961195671 [appSecret:protected] => f990f1213ece77863b10ed278067dc87 [user:protected] => [signedRequest:protected] => [state:protected] => 3c10e3f1d9f11e3757f5b02ac6fbe752 [accessToken:protected] => [fileUploadSupport:protected] => [trustForwarded:protected] => )
Its 6 hours in and all but one of the subthreads have ignored (or simply don't care?) that this guy and his various sites/media is either straight up crazy or disinfo. This guy literally has an hour long youtube video on "Agenda 21". A sibling comment notes that they "hope these sorts of blogs don't become mainstream on hn". Its kind of important insofar as any sense of community is involved to reiterate that. This is serious garbage, one can find any number of discussions of money, utility and politics ranging from any ana-cap to anti-cap. This is mindless tripe.
How unbundling Twitter and launching topic-based communities will win
Thank you for sharing this! I actually was naive enough to believe that WD would continue to let HGST operate as a seperate entity.

There is probably some good news in the article though, for what it's worth: "At that time John Cyne ran WD. He since retired, with HGST bss Steve Milligan taking on his job." ... "In other news Western Digital has announced a new executive management team, and it looks almost like HGST executed a reverse take-over of Western Digital." ... "A person who was close to the corporate action in Western Digital and HGST said: 'All key positions are with HGST people; it's a reverse buyout. First HGST took Coyne's money to buy themselves (probably with a clause that Milligan is becoming CEO) and then they watched WD dismantling itself.'"
yes, they've been asking people to test https for awhile as it now uses http/2
I always thought it would be an interesting physics exam question to ask: "If a clock were landed on Halley's comet, and retrieved on its next orbit, what would be the expected difference in time relative to an earth bound clock?" It's tricky because all orbiting bodies experience a range of velocities as they orbit their star. But I gather Halley's comet has a particularly eccentric orbit (0.9) with a rapid perihelion of around 70km/sec, an aphelion of about 1km/sec, and about 75 years for a single orbit (ΔT' = ΔT / sqrt(1 - (v²/c²)))
Go tends to emphasize the simple, imperative way to get a computational thing done. It goes so far as to never hide a for loop from you. I'm not experienced with lisp, but from reading sicp, it seems to be a paradigm built on creating stacked layers of syntactical sugar (dsls).
Correct, but this could probably be more clear.
In a recent job hunt, I found cases were used as an excuse for the company to invest 0 time in the process.

It was so bad that with one company (a unicorn, if it matters) I replied with a bunch of questions that I had to fill out the gaping holes in the case, and they instead opted for an in person to avoid investing the time in the replies! In two other cases, they requested 4-6 hours for a time commitment. I told them I was incredibly busy and was more than happy to put 1-2 hours into the case and return it as a work in progress. Both company's said to put as much time as I wanted into it, but then decided that the case wasn't complete enough to continue.

This last round taught me that I won't do cases as a first pass filter as a matter of principle. If you want me to do a case, invest time in me first so that I know we both have skin in the game.

These cases are really just optimizing for people with more time than others.
I really wish they had pointers to the source commits in their bug tracker. That would be fascinating :-)
There are trade-offs. Banks that hold all their loans to maturity get a benefit in knowledge of their borrower's true credit, but they lose the ability to hedge the idiosyncratic risk of their borrower base. (Example: A local bank in North Dakota that is holding all the recent mortgage loans to maturity may be struggling now)
I didn't downvote you, but you're probably being downvoted because jonathankoren was sarcastically mocking leesalminen's "the innocent have nothing to hide" attitude.
I wish they had explained how they utilize five dimensions in our three (or four) dimensional world. I could understand if five "tracks" of data were stored in a single physical stream, but that has nothing to do with dimensions.
Except it seems to be progressing exponentially, not linearly.
Lame title. Story talks about storing password hashes and not passwords. I'm still looking for a solution to storing actual user passwords. Scenario: All laptops in the company have a unique local administrator password. How do I manage this effectively as a domain admin?
It's free content, and they can sell ads on it.
Personally, I'd love to own it.
I've been writing some gocode recently and huge chunk of code is

if err != nil ...

I know you can do if ; err!=nil but that not that much better and you end up in deeply nested if blocks.

i have to mentally block out err !=nil to read any gocode linearly. How is this acceptable, I don't get it.

https://blog.golang.org/errors-are-values

We recently scanned all the open source projects we could find and discovered that this snippet occurs only once per page or two

This seems false from my experience, def way more than 1 or 2 instances per page.
What's your use cases where you've found startup time to be a significant issue?
You could try using Flask-Restless with Backbone-Relational and then integrate with something like React using something like https://github.com/magalhas/backbone-react-component

https://flask-restless.readthedocs.org/en/stable/

http://backbonerelational.org/
>so is debugging

Have you used delve?
https://github.com/derekparker/delve
They must have been aware that Enigma was broken, they had an agent in Bletchley Park [1], that part The Imitation Game did get right.

[1] https://en.wikipedia.org/wiki/John_Cairncross
The Ars article on this is actually much better than the Washington Post one:

http://arstechnica.com/science/2016/02/new-evidence-easter-i...
I think that mental health and work is something that's not talked about enough as a whole. If I don't feel safe making the journey to work in the morning then that's something that I want to be able to talk about with my manager. And if I'm not capable of doing anything more than staring at emails for a few days then it shouldn't be shameful to say that I'm suffering in ways that aren't physically obvious. It's so much easier to cope if you have a support network that includes your employer. Otherwise the shame and fear of being accused of making excuses to skive off of work can escalate very easily.
Well that was probably as frustrating to write as it was to read... The author does a nice job of forensics but can't really pin down the meaning on any particular OS.

My preference would be to have a well-defined, even if of-limited-use, load rather than a poorly-defined, but maybe-more-useful?, load. From the article, it sounds as if kernel authors tried to implement the former, found it difficult to do as machines grew and then everyone headed off in different directions only to implement lots of the latter...
This works once you have a (supportive) partner. It requires living in nice rural communities where you will never, ever meet a new person, though, so if you start it single you'll stay that way forever.

So I'm in a major metropolitan center, burning cash at a way higher rate, so I can hopefully find a wife. If I'm very, very lucky, that wife will want to move with me to rural Colorado.

Sadly, this insane plan is about the best I can imagine.
>People do wear thin soled footwear, and go barefoot indoors.

As I discovered myself, walking barefoot is utterly different from running barefoot, and no amount of walking around barefoot will teach you to run barefoot, if you are used to putting on shoes to run. And the 'thin soled footwear' people show me when they try to explain that they already 'run practically barefoot' is almost always too inflexible. I use $16 water deck shoes, myself.

It took six weeks of daily practice for me to learn to run properly barefoot - the process is very counterintuitive, after a lifetime of running in shoes. There are conditioning problems too: halfway through, I could neither walk normally nor 'barefoot' without some pain, because I didn't have the muscles to run barefoot properly - landing on the ball of my feet and pushing off with my heel (many people think that barefoot running is just 'running on your toes'. Do that and you will have a bad time).

Now that I have learnt to run barefoot, the other method feels difficult and unnaturally jarring, as it did, before I could run barefoot style.
Microsoft Azure Now Offers Red Hat Enterprise Linux, Container Management
Actually, I'm curious, but for slightly different reasons. Windows can still technically support other architectures than x86; if ReactOS is truly compatible (which it evidently is!) then I wonder how hard it would be for them to port the HAL layer to things like SPARC.
(It's listed under your profile picture in the top right; to get to your stars, just click it and choose "Your stars")
Release notes are here:

https://golang.org/doc/go1.6

Notably new this time is transparent http/2 support and tighter rules for integration with C.
> You can create a worker system, or use a child process to solve this problem, but most of these articles never mention it

Or you can do the bcrypt() inside your (PostgreSQL) database and add an extra layer of security by not directly exposing the hash (or even the whole password table) to the web server process (i.e. write a password check SQL function and allow only calling it, no direct table/column access).
"Tempelhof added that the Bitnation model will follow a radical interpretation of reputation where not just people, but also laws will have reputation."
> The concept that a person could not digest milk, one of the most basic foods, just never crossed my mind.

For most mammals, including, for most of history, most humans outside of a few particular regions, milk is only "one of the most basic foods" for infants.
What I meant was that Windows can have the good parts of both iOS and Android. To be clear: it can run as smooth as iOS while letting me access the file system as Android does. Another rant on Android: Developing apps for it is so bad... The guy that thought it was a good idea to destroy and recreate an Activity's after orientation changes should be fired. iOS's approach is 10000 times easier and faster

EDIT: Corrected when I said Activity's UI was destroyed to the Activity itself