skysight-inc/HackerNews huggingface dataset:
Probably Hotmail, since without insurance you won't be allowed to buy a car at a dealership, thereby reducing your overall likelihood of acquiring a vehicle, which in turn reduces the likelihood you drive, which in turn reduces the likelihood you crash your car.
https://news.ycombinator.com/item?id=16213280
> * Faster startup time (current container runs `gitlab-ctl reconfigure` on every startup)

Oh my god, how much I'd love that.

On the topic of cloud native charts, can I use the new cloud native gitlab chart (if I run an external prometheus, postgres and redis already separately) today? And how would I migrate?

And one thing I'd love to see is building docker containers without having to give the runner access to the host's docker. How do other CI solutions do that?
Sometimes people see this and start thinking that options or stocks should be regulated harder by the sec so employees dont get shady deals and screwed like this.

But there is a much simpler way to prevent this from happening altogether: let employees trade the shares they got from openly in the market. That way, you would get a market signal on stocks on startups and shady deals like this would get whistleblowed on the market long before they are signed.
The forum spam problem is easily solved if you ask a question during registration like: "What are the last four letters in the name of this website?" Anything that requires momentary thought from an actual user, and is specific to your website, will throw bots off.
We use google autocomplete for this.
With BitPay at least, you pay fees both ways. They'll refund you whatever they got minus the $40 of transaction fees to get it back to you. And of course they charge you the single-transaction rate, while they do a batch transaction that them costs much less (i.e. they are making money off refunds).

Happened to me a few weeks ago - I tried to buy something and it got confirmed, but not fast enough for Bitpay, and they cancelled the transaction. So I was out the fees both ways. It was unpleasant, but not surprising, given how shoddy the whole system is.

Everything is fees with Bitcoin - fees for transactions, fees for exchanges, fees for mining pools, dev fees for mining applications, etc. There are no end of middlemen, and they all have their hand out. Sure, each of them is providing some legitimate service, but it sure makes 3% merchant fees for Visa look positively cheap in comparison. And did I mention the instant transaction times, the fraud protection, and the complimentary hardware token that's accepted by millions of businesses worldwide!? Try a credit card today!
Devilbox: Dockerized LAMP/MEAN stack
Messaged you:)
I was going to guess that there are lower fraud rates in the EU compared to the US; based on what my former partner said, their company reports all EU fraud, but only fraud in the US over 2k USD. In addition to that, people in the US treat (abuse) consumer protections like a "get a free purchase/built-in scam protection", and try buying iphones for $260 on p2p apps from a complete stranger.

There could be something else there, though.
During the dotcom bubble I knew that VCs were kicking themselves every time some 'secretary becomes a millionaire' story came out because this meant they left money in other people's pockets. Over the last 20 years investors have refined their game and this never happens now, indeed, it's the opposite.

I think the only reason to go in other than as a founder in a startup is as someone right out of school for experience. Otherwise they have to be treated like any position, on a straight cash comp/benefits basis, ignoring the likely worthless equity scrip. In my experience, the best play is to go in on a contract basis once a startup is in the "burn baby burn" phase and you can bill market rate for all of those hours.
Don't think Lovelace did much in Engineering.

Besides, what was engineering at the time when AC power was invented? Steam engines and sewing looms?
The same can be said for Emacs with all the various packages and any elisp you write.
Various law firms have written articles about this: https://www.google.com/search?q=83(i)+tax+reform - consider retaining a lawyer yourself if this is relevant to you.

(Obligatory: I am not a lawyer, and none of my comments should be construed as legal advice.)
> We need regulation in place to stop any punitive decision making, public and private, which can be found in court to be based on correlation instead of causation.

Actuarial analysis for insurance to exercise a privilege (i.e. driving) is not something that needs to be more heavily regulated. This is not health care/insurance, food, housing, or other critical necessities.

Correlation is a core part of actuarial science. You'd actually destroy the insurance business if you regulated that into nonexistence as you desire.
Those with questionable/poor ethics ethics should be called out. There is no reward for staying silent while people/companies do wrong by others.
Go on a random terminal and fire up emacs. It isn't there. Also, your favorite editor isn't there. That's why. The practical choice is Vim vs. Nano or Joe or Ed or whatever.
Also, Dynamicland uses Realtalk, a programming language / operating system / protocol for physical computing that is more general than projectors/cameras/papers.
Not sure if trolling... Correlation does not mean causation
Right, but the $700m valuation was preferred, and the employees likely paid AMT tax on the FMV (about 10-30% of that value). It's certainly sad but at least they can write off the AMT loss against capital gains if they have any and wish to, or take the $3,000 credit every year.
I've met exactly 2 doctors who have actually used OpenEMR and they were both researchers. It is quite nice, but the last time I looked it wasn't trivial to set up and run. I think it one of those "it's free if you time is worth nothing" kind of things. And, there are some other EHRs out there that are nice and won't break the bank.
Is it? I run a mostly stock .vimrc and no editor will satisfy me.
where there is a play for global level marketplace you will see real competition (smart phones seem to be a good example here) ... Uber is basically alone at the global level because of the local advantage as suggested and also the unwillingness of other big players to lose hundreds of millions of dollars each year or ignore local laws.
4,000 cycles for a speculative execution barrier is just horrible.
Since everyone needs a patched kernel, might as well take the time to recompile the kernel with retpoline compiler and remove all offending instructions in the first place.
I can think of a dozen reasons for that, but here are a few of the most salient ones;

1. Reading and evaluating code in an unfamiliar context is really £@#&ing hard, especially on a complex project. Understanding someone's commits requires knowledge of the project as a whole, the problem space, the environment, etc. That's not possible to do for a large number of candidates. It might not give you a very good insight in to an applicant.

2. Most people's public code is of roughly equal quality (eg 'not great'). You can't really differentiate between people well based on it. What people do in their spare time for fun is rarely commented/tested/documented/etc, so it's a bad way to evaluate their skill level. If you find someone with good public code that's a great sign, but a hiring manager who's looked at 100 Github profiles and found zero good ones might reasonably have given up looking.

Also it could be seen as a discriminatory factor; if you think public code is important you're going to overlook people with little time to write any, eg those with families, care responsibilities, interests outside of coding. Building a great team is about hiring great people more that just great developers.

3. It's hard to trust someone's public code. It's trivial to clone a few open projects and take credit for the work, and a hiring manager doesn't have the time to dig in to everyone's projects to see if they've ripped the work off from somewhere.

Also, you may have dealt with 50 hiring managers who have never looked at your public code in your career so far. That isn't very many really.

I certainly wish there was a better way to evaluate developers skill, and as someone who has plenty of public work on Github I think it'd be great if that was a good starting point, but I don't think it's quite good enough yet. I can certainly see why hiring managers don't look there.
Personally, I'd rather car insurance were tailored as individually as possible. If I could get that option without my data ever leaving Google's silo, I would do it in a heartbeat. Then again, I know I'm very low risk compared to most people.

In general, I do think it's good that people pay insurance based on the real risk of loss they pose. I'm fine with this in the case of umbrella insurance, car insurance, home insurance, life insurance, etc. The only exception I have is health insurance, because I don't think people should die of curable illnesses, just because they can't afford treatment.

But if someone poses a high risk of causing a car accident, I prefer that they not be able to drive. If someone is likely to burn their house down (maybe they're into basement welding), they probably should have to pay more to insure it. Insurance companies know that many people would prefer to subject themselves to the panopticon to save money, which is why some of them are starting to offer the option of installing a speed tracker in your car, among other things.

I recognize that this is not everyone's preference of course, but you asked, so I thought I might give you some perspective from someone who thinks differently from you.
If I had a dollar for every time a recruiter has asked me to complete a code challenge within 5 minutes of my last push to GitHub, I wouldn't need to work anyway!
I have never understood the point of HackerRank. I even got into it with fairly high-up executives at my last job for refusing to fall in-line and use it as a tool. As far as I'm concerned all it does is exacerbate the already terrible hiring practices and hiring biases that plague the software industry.

I'm now CTO of a company operating a space that's as challenging as it is esoteric. We make hardware for adding by-wire controls to some existing cars to do autonomous vehicle test/validation. We make high-fidelity, high-bandwidth data capture software for AV sensor mules. We're working on a SDLC that enforces cryptographic chain of custody and produces safety-certification evidence as a continuous delivery artifact, and we're working on a high-assurance runtime environment for AV applications.

Hiring for this diversity of internal & external products would appear to be extremely challenging, but reforming/growing the existing teams and building new teams has proven fairly easy. Insofar as quality of new hires, productivity & growth of realigned staff, etc. is concerned. The challenge was in all the preparation it took to make it easy.

1. I never hire until I am absolutely certain I can identify and articulate a very specific need that aligns with a very specific set of goals.

2. I never hire until I am absolutely certain I understand the responsibilities and level of ownership required to meet those goals.

3. I never hire until I have a meaningful frontier set of models for the personality profiles (fallabilty acknowledged) that are likely to align with both those responsibilities and of the people they'll work most closely with.

4. I have candidates pair with someone or someones they'd actually work with on an actual problem being actively worked on by the team. Why contrive a pointless artifice like programmer-trivia---to guess at what the person would be like on the team---when I can make them an honorary member of their actual future team for a couple hours on-site or over video/screenshare?

5. I don't try to get a bargain on my hires. If I've managed to do all the above, then I know what I need, I know what it's worth, and I know how I need to manage my financial constraints.

This is my problem with things like HackerRank. It's just a thing that hiring managers can hide behind as a kind of faux-rigor to produce a completely meaningless "score" as though such a complex thing can be distilled down into a single number and used as some common metric for comparison.

Hiring is too important to the company, the team, and ultimately the candidate---whose livelihood you now partially hold in your hand---to be so fundamentally lazy about it.
Really cool, you don't really need to list all the emacs commands in the Readme. Even if is where most of the work went.

I would love to help. I can try to implement some of the pry features into Fir or work on a Rails integration ala pry-rails.
"since the peanut gallery is paying lots of attention it's probably worth explaining it a little more for their benefit."

what a ridiculous sentiment to defend a patch from Intel thats effectively disabled by default for one of the most egregious bugs in microcode since F00F.

"The new microcode from Intel and AMD adds three new features."
No ones talking about AMD, David, not Linus and certainly not hackernews or other outlets. Spectre patching will happen regardless of this fiasco but This NOT SPECTRE.
this is a taylor made shit sandwich thats been warned about by researchers and lurking on Intels plate for more than a decade. intel chose speed over security, and intel lost. Now they're trying to find a way --any way-- to avoid having to eat an 8 generation recall or worse.

its been said on HN before, but this is now more of an 'if not when' of intels loss of dominance in cloud. customers no longer care about the fastest chip in the west if its going to get neutered to half speed due to wreckless design that allows for a complete security disaster. Theyll buy twice as many AMD, at half the price of intel, and make up the difference in sheer volume.
So you think it would be better if insurance companies knew exactly all the details of your life so they could custom design your premium for you? Because that is the real outcome of making premiums specifically catered to your life experiences as opposed to general buckets.

If everyone were charged the same premium, your premiums would actually be much more, because now you would be deemed as posing the same amount of risk on the road as a person who has caused 5 accidents over 10 years.

You can't have your cake and eat it too.
>The idea that they should ditch HotMail for the functionally equivalent GMail just because GMail is popular is, of course, idiotic.

I think the "functionally equivalent" part is quite arguable, at least it was in the past when many techies made the switch from hotmail to gmail.

People switched because the features and interface were far superior.
I am a newb and so far didn't care much about the editor I used. How do I learn vim? Any good resources? Do I need to memorise a lot of shortcuts?
You probably better using Bash for Win 10. It's native now.
gold has intrinsic physical properties, yes. that does not imply a particular intrinsic value to humans relative to other things humans could be exchanging things for.

you could say that the reasons for valuing gold probably aren't going to go away anytime soon as far as anyone can guess. though even then, the market value of gold has fluctuated by a factor of like 10 in recent history as the durable abstract reasons for wanting it have not apparently changed as much. did anything intrinsic about gold change from 1980-1981, when the price crashed 82%?
Facebook, Google tell Congress they're fighting extremism withcounterpropaganda
A Conversation about Teaching Software Engineering
Exercising an option isn't the same thing as cashing out.

I mean, it generally should be (in the sense that you exercise to sell) but some people don't realize that.
Nah, his post is what Hacker News is for; if the company and their CEO is announcing coming out of stealth mode and answering responses, it's worth that guy vocalizing that potential vulnerability.

Your post tried to chastise him for calling out a vulnerability, and then tried to shame him for not quietly emailing their security team. Chances are if someone were a bad actor they would have:
A) seen that themselves outside of his message, or
B) Found out through sheer luck and brute force

If anything, the poster mentioning it invites the team to fix it before someone exploits it. It's worse to blunder on a hole someone told you was 1.5km down the road, so hopefully they either address it or fix it
I think the troubling aspect here is that these are actually statistically sound decisions. The company does not need to have a strong implication that Hotmail -> bad driver. They only need to know that P(bad driver | Hotmail) > P(bad driver | Gmail). And through some correlation (many of the theories proposed by others seem plausible), this apparently holds.

As developers of these systems, we need to be careful of how we might apply superficial correlations like these, so that we don't cause harm and burden to those who happen to be caught up in them through no fault of their own.

As a side note, I happen to have a 10+ year old Hotmail account that I use for signing up to services. My Gmail address is only given out to real people. Personally, I view it as a testament to my diligence that I have managed to give my email out to hundreds of websites, several of which have had database breaches, and still only see one or two unwanted emails per week.
Looks like Quri (https://angel.co/quri-1). All you had to do was Google OP's handle and dig into where they worked recently that had their characteristics
Not everyone wants an IDE, though. Unix is my IDE, and Vim is just my text editor. I learned emacs first and left it for Vim.
There's a simple technique to "control for" those factors. First you split your population into groups that each have a similar race, gender, and age. Then within those groups you make comparisons of the hotmail users to the others. https://en.wikipedia.org/wiki/Controlling_for_a_variable

You would need to keep in mind xkcd #882 (https://xkcd.com/882/).
Ruby seems to have a footprint on Hacker News disproportionate to its general popularity and TIOBE index. Why?
> But wait, why did I say "mostly"? Well, not everyone has a retpoline compiler yet... but OK, screw them; they need to update.

That got me interested, who has reptoline support, and from when?

GCC added support in 7.2 [0], which means a lot of people don't have access yet.

LLVM added it in D41723 [1], but I don't think that has landed in a release yet.

I can't find any talk around TCC, but that isn't exactly surprising.

Haven't heard anything about MSVC, and can't find anything, but that's not surprising as I don't think Windows is using reptoline in their mitigations, but I really have no idea.

[0] https://www.phoronix.com/scan.php?page=news_item&px=Clear-Li...

[1] https://reviews.llvm.org/D41723
Maven on Java 9 – Six Things You Need to Know
Still waiting for those credible sources!
If you can explain why it is OK for car insurance to charge differently by gender, but by race is not OK, I will be impressed.
Hold up. They asked “Vim or Emacs?”, not “What’s your favorite editor?” That’s why the answer distribution looks like that. I think we all know there are more normal text editor/IDE users than vi/emacs users.
I don't necessarily disagree with you. I posed that question because if Google actually did provide that kind of service, people here would be up in arms against it.

And god forbid if Facebook or Uber did [mind you that Uber is in a reasonably good position to], they would be sharpening the guillotines and calling for Zuck's and Travis' heads.
I have never used vim/emacs before. While sshing I end up using nano. Does the job. What advantage does vim have over nano? Honestly curious.
What happens in your case if an entity is not in any way "aware" of people's protected class (they don't collect that info) but using these other properties coincidentally affect a protected class?

Say you _don't_ collect info on people's religiousness but other properties you collect in effect result in you either discriminating for or against either religious people or perhaps against atheists.

If there is no awareness, is there still liability?
Sidenote : The background images are '3D' fractals, I remember reading about in HN itself a few years back. There was a fascinating article about a programmer writing about the steps he went through to get a 3D fractal.
What I'm really keen to see is truffleruby receiving a lot of community support.

The underlying JVM and the Truffle/Graal/SubstrateVM is the product of millions of man hours of research - and for the very first time, you have a compiler framework on top of that.

The Truffle framework also brings in a lot of support that all languages get for free, like zero overhead profiling https://twitter.com/nirvdrum/status/948333404122214401

Truffleruby is already in the running in benchmarks, and it will be awesome to see how far it can be pushed . http://nirvdrum.com/2017/02/15/truffleruby-on-the-substrate-...
In New Proposed Subway Elevators, Some See a Terrorism Risk
Like those who are of a certain gender and are charged more?[1]

Or those from a certain zip code who are charged more? [2]

Or those who drive a certain car model who are charged more? [3]

How is email address any different?

[1] https://www.nerdwallet.com/blog/insurance/teen-boys-high-car...

[2] http://www.latimes.com/business/autos/la-fi-hy-ten-worst-zip...

[3] https://electrek.co/2017/06/05/tesla-owners-insurance-rates/
If the price of housing always increases, how is anyone who's younger than you (and not richer than you) supposed to be able to afford a house?
17 Tips to Improve Your Online Sales
When the U.S. Air Force discovered the flaw of averages (2016)
You can't always sell the share after exercise. You're taxed on the spread between strike price and fair market valuation as income on exercise, not on sale.

There is an exception around taxes for ISOs that recently became useful with the AMT change in the new tax law, but even in that case you often can't sell the share after you've exercised it without permission from your private company (which you are very unlikely to get).
Let me ask some clarifying questions, because I think I understand the broad strokes of what you're saying, but I'm not clear on some details.

OK, so I find that among Black users, Hotmail is associated with a 1.05 relative risk to the baseline, and among white users, 1.15 relative risk. How do I then apply this knowledge to an incoming user of an unknown race with a Hotmail account? Do I give them the population weighted average of of the relative risks among all my buckets? What if I do know their race? Do Black users get assigned 1.05 as much risk and white users get 1.15?

Also, what if some of my buckets aren't full enough to get a high confidence of the relative Hotmail risk in that bucket? Let's say I don't have enough gay Hispanic women in my cohort. Do I just drop them from the analysis and hope they're similar to the other populations?
I'm not sure how close this is to the retpoline mitigation but ... https://blogs.msdn.microsoft.com/vcblog/2018/01/15/spectre-m...

Our tests show the performance impact of /Qspectre to be negligible. We have built all of Windows with /Qspectre enabled and did not notice any performance regressions of concern. Performance gains from speculative execution are lost where the mitigation is applied but the mitigation was needed in a relatively small number of instances across the large codebases that we recompiled.