skysight-inc/HackerNews huggingface dataset:
... and a similar experiment in predominantly Han Chinese China likely results in the same thing biased towards Han Chinese, In Thailand towards Thais, and in Cambodia towards Khmer people.

My GF lived in China half a decade, and she had trouble with tailored clothes, because they could never accept her southern-European proportions.

The idea that the most common size should be the most common group is just business 101 (build for your customers).
> Only squash when it removes bug that only ever existed on your machine. Everything else should be recorded in the history.

You can squash into master without losing the history of the code review with git. This gives you the best of both worlds, a more accurate history than the one you propose, and a master that isn't broken.
I don't see why VR should be isolating. Just because you're not immediately available to the people immediately around you doesn't mean you aren't available in a very personal way to many, many more people. VR is going to enable "face to face" communication across continents. It already has, it's just a matter if penetration now.

And VR doesn't cause nausea. Bad applications cause nausea.
I've done it recently as an employee of an acquired company. In addition, acquirers can (and do!) interview the developers as well. We got questions that approximated how one would take git and turn that into the running system. The acquirer also crawled through all our software license agreements; wee discovered we weren't licensed quite correctly for a commercial db, so had to rip it out in a real rush.

For each customer agreement, it has to be either assignable, or you will have to go to that customer and get them to agree to make it assignable. Each customer that doesn't so agree, or each customer that is slow to respond, will have to be individually negotiated with the acquirer in the period before the deal closes.

I'd imagine that one of the big risks acquirers of small companies care about is the company somehow fucked up and doesn't own, or there is a colorable claim they don't own, their source code. Having an overlap of git commits with your previous employer could cause you a lot of heartburn at minimum. And good luck getting a timely response from your previous employer that they don't own that code. Your previous employer, even if they have no intentions of being dicks, simply have no incentive to sign (and definitely no incentive to promptly sign) such an agreement.
I'm not even sure why we're even talking about it. it's irrelevant. "Fixing it" wouldn't delay the problem by a day. There are 100,000 commercial flights every day.

https://www.quora.com/How-many-airplanes-fly-each-day-in-the...

We need to fix the big problems, not the irrelevant ones.
This is a good quote from http://martinfowler.com/articles/web-security-basics.html

The modern software developer has to be something of a swiss army knife. Of course, you need to write code that fulfills customer functional requirements. It needs to be fast. Further you are expected to write this code to be comprehensible and extensible: sufficiently flexible to allow for the evolutionary nature of IT demands, but stable and reliable. You need to be able to lay out a useable interface, optimize a database, and often set up and maintain a delivery pipeline. You need to be able to get these things done by yesterday. Somewhere, way down at the bottom of the list of requirements, behind, fast, cheap, and flexible is “secure”.

------

I'd add to this list, if you are doing a side-project: marketing, SEO, customer acquisition, advertising, customer support, infrastructure support, ...
Bangalore, India. Many Positions. Full time.

I have taken up a role to build a payment network from scratch, out of Bangalore, India. It is funded by a big corporation, but will be arms-distance from their central business.

It is a large, complex and fascinating problem to crack. The potential to bring banking to 600 million un/underbanked Indians is what excited me to work on this.

We are looking to hire a good core team of full time math, physics and CS majors, UI UX and product managers, who will work of Bangalore, India.

We are open to hiring people from around the world but they will need to work out of Bangalore.

I have posted and have hired a few good candidates from Who's Hiring threads.

Since my first post, we have now released a product and also secured a payment bank license.

We also have our payment network baked into banks and mass transit.

In the past I have built both fast-data and big-data companies and have a few patents in this space.

If you are interested, please email me at google's email service - takenottie. Thanks for reading.
It's also the case that you lose the code review if you force push to a PR's branch after adding in a typo fix and squashing locally, right?

That's a pretty good reason not to squash till the review is done.
Cool, thanks! I'm going to play with it if ya'll dont mind. :)
I use commit amends (`git commit -a`) for continually updating these pseudo-stash commits.
It looks like in his studies the results have been that ethnicity [in combination with people's guestimates?] is a better predictor of a person's shirt size than people solely providing their own measurements. That's definitely an improvement. It's possible he could use Kinect or the like to get even better information for creating better fitting shirts.

Still, if this current method is more effective in predicting shirt sizes, I really see no reason not to use it.

Would people have an issue with integrating more diverse ethnicity studies into pharmacological studies? Probably not. So I don't see why it would be different here.
If CloudFlare keeps blocking Tor, the blocks will be circumvented. Unfortunately, it's the assholes who will figure that out first. But so it goes in war.
In a few weeks we are having the DC-Baltimore Perl Workshop (in Baltimore on April 16) where there are a few talks on Perl 6. Join us! http://dcbpw.org/
> Everything else should be recorded in the history. Forensics are important to the long term health of your project and you impoverish yourselves by scrubbing the crime scene.

OK. So would you support an IDE that generated one individual commit per keypress? When I type "hello", that's five individual commits each changing a single letter.

That is the true history of what happened, and it's typically recorded in your IDE's undo log in memory, such that you can step back and forward through it. Are you OK with pushing this commit history to your project? That's the true history of what happened, after all, and it could be forensically useful.

When we commit code to share it with other people, we recognize that only a certain level of detail is relevant to them. The physical sequence of letters that I pressed isn't typically relevant to someone else. Rather, the logical set of changes is what affects them.

If you agree that a single commit per letter of keypress is undesirable then you agree with me in principle. There is a finite level of detail that makes sense to share, practically, with current source control systems, and what we're arguing about is how much to share.

I feel like this is important to point out because people frequently make this argument about the "true history" of source, and all that, while neglecting the fact that the commits they choose to ship are already an arbitrary simplification of the "true history".
San Jose City Council Approves Smart City Vision Framework
I don't know where this lies on the "credit-to-google-credit-to-ddg" spectrum,

but you can search `!gyear bug` on DDG to get google results from your query within the last year. `!gmonth`, `!gday` also work iirc.

edit: Unfortunately, something like `!dyear` doesn't work for DDG.
that's more of how squash was applied in the situation ... If they had huge commits then while squash might break it up a bit that's a problem with how the people did their work.

Myself I like to do PR and merges with code that can be logically comprehended quickly and doesnt break the build.

a lot of that is due to being emphatic to people that are doing the reviewing. I know they don't know the context as they aren't in the code so I'm showing them a snippet of it, say a new method in s single commit. Then another commit for another method. Finally a third one that actually does some new functionality by combining the two.

I figure that's good enough for people to see that unit tests passed on the two methods and that the system started getting errors after the last commit so to look there for faulty logic.
I worked in men’s clothing for quite a while, and I have an anecdote to report about customers self-assessing their size and cut. If you sell people what they ask for, they will hate you for it.

In my day, off-the-rack shirts came in a collar size, an arm length, and there were three cuts: tailored or “european,” standard, and “full,” for the pear-shaped gentleman. People sized themselves at least an inch too small on the collar, and would woefully under-report their arm length too. The problem, of course, was that as you gain weight, your neck grows in girth and you need a larger collar.

What about the arm length? Well, that’s measured from the nape of the neck to the wrist. As you gain weight, you gain fat and/or muscle around your shoulders and upper arm, and that can increase the measured length of the arm, even though your skeleton remains the same. Customers would ask for a shirt in the size they wanted their neck to be, and if you sold it to them, they’s squeeze into it, there’s be an unsightly bulge, and they would decide that your shirts were unflattering.

One of the tricks in those days was to report that a particular shirt’s measurement was more accurate in metric, so if the customer didn’t mind, could I take a metric measurement... And I would sell them the correctly sized shirt. Although it was larger than they requested, it would look better because it fit properly, and they would see a thinner, fitter person in the mirror.

Needless to say, the exact same thing was true in the cut of the shirt. The endomorphs would ask for a standard, and the standards would ask for the tailored cut. And then they’d hate the shirt.

The best thing was to report that this particular manufacturer was off on their sizing, and just hand them the short that you could eyeball was right for them. They’d be back for more.

So where were we? Oh yes, you absolutely cannot rely on people self-selecting their body type. The best thing is to measure.
Although I did enjoy the article, I was thinking it was going to be about literal noise levels. So I did a quick search and found a map of that:

http://www.nature.nps.gov/sound/soundmap.cfm
How has hacker culture changed? Not at all. I've been living, breathing, eating and drinking (less these days, tryna clean up my diet) the hacker culture, hacking continuously since late 1980s. Linux and Windows NT were of course the biggies, but after Windows XP it's been a meh fest turning into cringe fest, and Unix never changes.

One thing has changed: nowadays you can be even more reclusive and asocial than in the early, diskette-swapping, meatspace-meeting days.

Hacking will always be the same activity despite having more code at your disposal. Keep on hacking relentlessly and one day you'll make a sweet hack. Only then you truly understand what it is to be a hacker.
Warning: this site makes your computer run slow and hot
I'll list some things I do in slack that I don't in IRC. Many of these are probably possible in IRC, but the fact that I don't do this in IRC suggests that there is more friction than slack.

1. Send messages to people that are offline.
2. Easily see unread messages in a channel.
3. Markdown formatting.
4. @everyone/@channel notifications (not to be abused).
5. Simple Github integration (and other apps).
6. Mobile notifications (in fact, just the overall state of "mobile")

I'm sure every single one of these could be added to irc via bot or something like that. The beauty of slack is that I can set up a slack team and do all of the above without having to really muck around with that. Much lower operational overhead.
Yes, that botnet dig is bullshit. Some botnets use Tor for C&C. But jerks don't need botnets to have lots of Tor exits. That's what VMs are for. Botnets give you lots of residential IPs.
I don't find "seeing how the sausage was made" simply of interest. It's often very instructive.

Often there will be counter-intuitive bits of code that make sense in "git blame" if you see the original, small, commit that they were created as part of. If they're part of a 1000+ line feature bomb, you lose that important context.
I'm confused why you use the phrase "GNU/Linux" but not "free software". I've never seen someone use that combination before.

But as to your point, not all free software licenses are copyleft. The MIT and BSD and Apache licenses are all proprietary-friendly licenses.

And as for requiring to extend the GNU/Linux ecosystem, I don't think that's true. It just looks like they've implemented syscall compatibility with Linux (something that FreeBSD has had for donkey's years and SmartOS has been working on for the past few years). Neither of those technologies resulted in more software specifically for GNU/Linux.
I've often wondered if it would be possible to design a source control system that could track this lineage. Kind of like, "inside" of a commit would be a hidden history that you could unpack if you wanted to. "This single commit is actually the squash of these other commits made by this guy". "This commit is actually the rebase onto mainline of this commit a guy made when his machine was behind". The commit would look like normal to the current source control CLI, by default, but would reveal this hidden level of detail if you inquired "How was this commit made?" - then you'd get the reflog.

I've wondered if support for a feature like this could finally resolve the "debate" between merging and rebase. The people who like having the full history (whatever that means) would have it, and the people who care about logical changes would see it by default. The cost would be that the repo history would indeed have the full level of detail, but you could imagine supporting a cleanup operation that erases this "origin" information for commits that are sufficiently old, or else simply doesn't pull the info by default and fetches it only when necessary.

(You can kind of simulate this using merge commits, by only looking at one parent, but it doesn't really work out well in practice.)
Has it been reliable ? We are testing with a few users but curious how it works at any kind of scale ?
I was always amazed by .kkrieger[1]

You get an FPS complete with 3D engine... dynamic lightning IIRC (!), music, textures...

... in 96kb.

Granted, most of it is procedural but still it's a very very impressive piece of code.

I've always thought that demoscene guys were on a whole different engineering league

[1] http://www.pouet.net/prod.php?which=12036
How to remove duplicates (controlled false positives) in large datasets
And football coaches.
> I think he has a full fledged beard making him not fit into the neckbeard type.

> RMS was foresighted enough to make licensing a core part of open source. I have a deep respect for the man.

He founded the free software movement. The open source movement is based on different values (convenience above ethics) which Stallman doesn't agree with.

> The Achilles heel for open source software remains to be patents. In that regard I think many proprietary players still have the upper hand.

Both the GPLv3 and Apache solve this problem. The issue is that too many people are using permissive licenses where it's not appropriate.
Thanks! Funny story: I pitched an early group of investors this idea, and they stopped me and asked me why I settled on this name. I replied, "Because the domain was available." and the entire room erupted in laughter. Pretty solid experience.
> Yes partycoder, it sure would be interesting to hear what "neckbeard" RMS has to say about this move by Microsoft today, would it not?

Ignoring your insults toward RMS, you can always send him an email at rms@gnu.org. He responds within a few days most of the time.
Email didn't outrun the bear. It outran the other hiker.

The honeypot space for spam is now systems other than email. Social media. Blogspam. Web advertising. Dating services. SMS.

(I'm not sure precisely which, but pick from among there and you'll likely turn up the issues.)

Email is fairly well defended at this point, though not without considerable collateral damage (small / self-hosted email is quite difficult, most of us rely on a small number of high-volume providers who may present a considerable privacy risk).
I've been using nixpkgs for almost a year on an age-old linux distro controlled by my company. It replaced gentoo-prefix, which was error prone and hated RH based distros.

Nixpkgs works really well and the separated environment makes maintenance easier to control. It occasionally breaks upgrade of some packages, but it never affects the working environment.

It seems with 16.03 they are bold enough to go gcc 5.3. It would be interesting to test out my toolchains against the gcc 5 series, but I still don't see gcc 5 being the default on the Nixpkgs. I guess I'll wait a bit longer to waste my time on gcc 5.
I have a really hard time believing they had to triple the number of administrators due to government regulations.
Probably leases? They only offer leases on the Model S AFAICT.
How do we know that you are correct? Maybe universities do have bloated staffs. Salaries, benefits, retirement are going to be a lot more costly than nicer dorms and a fitness center.

People are offering solutions without following the money.
The joke (I think) being that Apple doesn't upstream a lot of code.
I think P is assuming that these kinds of gadgets will rely for a while on processing done somewhere else closeby in order to shrink them further, sort of the Apple Watch crutch. This assumption misses the problem you have with latency - the refresh rate of VR/AR needs to be extremely tight for these objects to really stay in one place when you walk around at even a modest pace. So the limiting factor isn't just processing power and weight, it's power+weight+latency+price that you need to balance, with hard limits on latency and weight.
Try Scandinavian shoes. Finns in particular seem to have built-in snow shoes, so Karhu runners are extra wide to accommodate their client base.
I suspect the problem could be eliminated by taking a few more measurements.

Whatever is systematically wrong that correlates with race is a form of error. You know that it's wrong because it is measurable. If it is measurable you can just turn it into a measurement which compensates for the error.

How about giving users a choice: workflow A with fewer measurements plus race question, or workflow B with a couple more measurements and no race question.

I suspect you have to get a circumference around the shoulders, the chest under the arms, the waist around the navel and around the hips-butt. Also, the circumference of the upper arm and neck circumference. If you have all these, I don't see how you can possibly mess up a T shirt fit.
It's literally the exact opposite of phrenology.
I think people understand Roman's point -- they're simply disputing his first paragraph, namely that:

- the code is "awful"

- the programmer "doesn’t know basics"

- "goto statement in C" is somehow anathema
Actually they are a special type of Monad which is a functional programming concept (see Haskell).
You left Debug = True on your production site.
e.g. http://www.sixtostart.com/onetoread/2016
Ignoring the racial issue for a moment, I don't understand how they ended up with the questions at all.

> Naysayers told him that when customers input their measurements, they often made mistakes — the idea wouldn’t scale.

> Asking about waist size was insufficient, for example, because it gave no indication of the size of one’s midsection. So Skerritt added a question about how far one’s belly protruded. Other questions were too confusing, like one about how T-shirts fit around your chest and shoulders.

1. There are dozens of fitted clothes manufacturers. More every year. It doesn't look like they fail, or not scale. I see almost only positive reactions about them on twitter.

2. Of course trivial measurements will not be enough. The article gives the example of midsection. But that's not other services ask for. Tailorstore asks for either common t-shirt size, 2-3 measurements, or if you actually want a fitted shirts, you provide: neck, chest, waist, hip, seat, shirt length, shoulder width, arm length, wrist. No need to ask about hanging bellies - just ask for measurements.

When they ask extra questions they seem to derive some ratios between basic sizes. Maybe it works, maybe not... but did they actually find out that taking own measurement doesn't work? I ordered some tailored shirts online, gave all my measurements and couldn't be happier with the result. Are the extra questions actually worth it? Maybe they did verify that, but it's not in the article, and I find that really annoying - here's the solution to what people told us will be the problem, we're not going to tell you if we verified that it is a problem.
Electronic Arts unveil new free-to-play business model
Why 44% of workers can’t sleep at night
"Netflix critics acknowledge that the FCC's net neutrality or "Open Internet" rules apply only to Internet service providers and not content providers like Netflix. "

What's to stop companies like Netflix from making deals with service providers to essentially get around Net Neutrality? There isn't any real way to stop this, because it is their content and should have full control over the streaming of it.

As a side note, Net Neutrality supports really don't seem to understand the laws they worked so hard to get passed.
The only difference between what I said and what you said is that you've added that MP training emphasizes deescalation. Both MPs and civilian police observe the same force continuum, but it seems to me that MPs are simply more disciplined. I don't think it is realistic to try and bring regular cops up to that standard of discipline, it would be much easier to simply provide a less flexible justification for violence. Many years ago when I was in USMC security force I remember being trained on actions that nudge the escalation of force - which was likely the first time I heard the phrase "furtive movement". While I'd seen a fair amount force applied subsequent to that period of instruction, I never heard that justification used. It seems to be the go to justification outside of the military.

My point is that giving cops the latitude that the escalation of force provides is like giving the CEO's 15 year old nephew the commit bit and letting him write safety critical software in non-MISRA C.
What is the salary like?
Show HN: Unlimited message search and conference call for slack FREE plan
So the problem with categorizing people into races is that there are many axes along which people can be divided into buckets, and any particular race grouping only has meaning in a particular place and time and will have totally arbitrary boundaries, which are as much cultural as they are genetic and physical. As long as people understand that, it's okay to talk about races tending to have certain qualities. Because culturally we've divided people based on those qualities.

But it's really important to understand that people of different races aren't different kinds of people. Any more than people who have blonde or brunette hair are different kinds of people.
Pirate Flag
That's what the author of the pull request should do. But this provides a potentially useful alternative when that doesn't happen.