skysight-inc/HackerNews huggingface dataset:
Believe it or not you can actually look this up yourself. The impact of board size on corporate performance has been pretty thoroughly researched.
This is an interesting perspective but knowing Japanese culture, it's more to do with risk aversion and losing face by announcing something and then having it blow up in public. Very different environment.

In the US you can commit white collar crimes and still have people invest and give you the benefit of the doubt. There's no sense of shame rather glee and glorification, the i-get-money-fuck-you attitude.

In Japan, people will commit suicide for way less or even perceived wrong because there is a great deal of shame imposed on the individual for fucking up. Tough to innovate when failure is so taboo, people are willing to remove themselves from earth.
Buzzfeed really do produce some first-rate journalism. Their investigative work is absolutely equal to anything being produced by traditional newspapers.

https://www.buzzfeednews.com/investigations
ORM's "simplify" things until something goes wrong, then they can be a pain to troubleshoot. A "light" set of utilities can also simplify a good portion of the database interaction. However, they don't give you a false sense of power such that you tie yourself into a knot that bites you 3 years down the road. But, it depends on the shop: If your shop always has a couple of good ORM experts around, then they can deal with and/or avoid such snafus as they happen. But, it's hard to "casually" use ORM's right.
I've occasionally had a moment of schadenfreude where, after interviewing at a place I hated, I could write something like this:

Dear <So-and-so>,

Thank you for considering me for <position>. I certainly enjoyed talking to you in person. Unfortunately, I feel that <company> is not a fit for my needs at this time. I wish you the very best of luck in your candidate search.

Sincerely, etc.
If only the journalists that reported these stories in 2017 at BuzzFeed were real:

* Helping to free an innocent man who'd spent 23 years behind bars

* Exposing the true scale of Russia's targeted assassinations in the West — and how UK and US authorities have turned a blind eye

* Sexual assault at Massage Envy

* A dirty offshore bank — and its blue-chip Western enablers and protectors

* BP's dangerous accidents in Alaska

* The US government's shadowy national security contractors

* Whistleblowers: FBI software contains Russian-made code

and more: https://www.buzzfeednews.com/article/markschoofs/the-year-in...
There are some interesting comments in this thread. I still think that rents would absorb a lot of the value from UBI, but I'm starting to think that UBI might work from the perspective that injecting money into the system so that it is captured by lots of small landlords is a better alternative than injecting money into the system so that it is captured by large corporations and then hoping that it's going to trickle down.

Capital naturally wants to aggregate and trickle up, not trickle down. So if most of the newly minted Fed money was injected at the bottom (instead of at the top as is the case now), it would probably flow through the whole system more efficiently.
100 installs from 10,000 visitors for starters.
I believe he's trying to say that it's just impossible. In movies heroes uncover government conspiracies and culprits get handcuffed. In real world nothing happened. Snowden is now a cultural reference for comedy:

https://www.imdb.com/title/tt6663582/
Life Without Water: Sweaty, Smelly, and Furious in Caracas
I think there’s a way to make motors without permanent magnets
If there is anything I have learned from being an owl, it's that larks are self-righteous jerks.

The reality is that the first person to wake up sets the schedule, because they can prematurely awaken anyone that is still sleeping. If you go around clattering around in the kitchen making coffee and bacon smells at 6 am, you can wake me up and I have no recourse. If I wake a lark up at 2 am, before going to bed myself, they can take revenge by staying awake and preventing me from sleeping at all. They have us by the clocks, and they know it.
I actually agree with both of you, _as long as it's up to the implementer_. I see requirements specifications that deliberately try to remain vague in the hopes that the developer will produce a "general" abstraction that can be reused - and always end up shooting themselves in the foot by never saying exactly what they want done. Or the "disruptive scrappy startup founders" who want you to build "legos".
If Epic had silently released the patch and not responded to the thread, that would be irresponsible and unethical, be harming the security of their users and be spitting in the face of the responsible disclosure community - that's something that you can do once, demonstrating to the world that they explicitly refuse responsible disclosure and every security researcher should publish Epic's vulnerabilities immediately without notifying Epic first.

And it's not like they would have succeeded - you can't patch something silently, if you know of a vulnerability it's not that hard to verify if it has been fixed in every upcoming version or not. Google would have had noticed that within a day anyway and (with justification) disclosed the vulnerability right then and there, instead of giving them those 7 extra days.
"Media wearout indicator" was recorded for OCZ drives, IIRC.
I wasn't trying to put words in your mouth, it's just what I could conclude from this put in context:

> It wasn't hindsight: we've been publishing and describing these risks along with techniques to mitigate them for decades.

>https://news.ycombinator.com/item?id=16092183

It worked for decades and the issues were "ignored" (not given much of a second thought) because everybody assumed that's all there is to the exploits. Corner cases that can be easily mitigated in software. It's just when everybody realized that the whole implementation in hardware was broken that the point was driven home.

Performance is what sold those CPUs when security just couldn't. Without the critical mass of revelations recently I doubt security would have been considered too much today. Just like privacy became a concern only with a similarly shocking volume of revelations.

So looking back it's hard to say if Intel would have chosen another way. Yeah, in hindsight you could say "if they just fixed it back then..." but in reality nobody would have cared.
You don't have to change from the qwerty layout for general typing.

For example, you can program the keyboard in such a way that pressing X+A sends Ctrl+C keys to the OS, where X is a custom modifier button (Not Ctrl but a separate button that you assign for this use case) and A is, well, whatever other button on the keyboard you want to use for this, not necessarily "C".

Or you can have a single button programmed to send Alt+Tab, or... whatever, really, the firmware is very flexible.
> sin might be rather expensive on your GPU targets

Definitely depends on hardware, but I learned recently that on my NVIDIA GPU, the transcendentals are actually in a separate pipeline, so they are free as long as you don't do too many of them! The 3 term sin approximation in the article might be slower than calling sin(), on my GPU it'd crowd the arithmetic pipe.

> This is very similar to a smoothstep, which explains why smoothstep techniques for this kind of filtering works so well.

Seems like most of the filtering I see in ShaderToy uses smoothstep(). I sort-of assumed it was a hack of convenience and availability, but it's nice to see there's some justification for using smoothstep! I'm tempted to try this pseudo-bandlimited filtering on ShaderToy.
GloFo is long-term sustainable, just not as a leading edge foundry. Old process tech doesn't go away, they just move to producing lower-margin products. 65nm is still in mass production. 14nm and, more importantly the fdx processes (as they have lower chip development costs and therefore are more attractive for the low-end market) will still be in full production 20 years from now.

Just not making fast cpus.
On a similar note, Fishman produce a range of electric guitar pickups that use stacked PCBs for the sense coil, rather than the traditional loop of enamelled copper wire. It's not necessary (and it's undoubtedly more expensive), but it gives them far more precise control over inductance.

https://www.youtube.com/watch?v=oZSS13d3vZs

https://www.fishman.com/products/series/fluence/
Sorry, but have you ever worked in a bigger company?

The problems in a company are obvious for most workers.
Maybe they just would pull money away from shareholders and executives in the form of pay raises and better benefits for senior employees, particularly the ones who run the union (https://philip.greenspun.com/flying/unions-and-airlines). Also, by enforcing a closed shop, they could simultaneously pull money away from lower level employees, in the form of union dues, and funnel it to the benefit of the people who run the union. Sometimes they even funnel the money to the Mafia (https://en.wikipedia.org/wiki/Jimmy_Hoffa).

The moral hazards inherent in a "handful of powerful leaders who represent the interests of $GROUP" doesn't change much when $GROUP is "workers" instead of "shareholders". Executives and union organizers are often two sides of the same coin in that respect.
Hm, it did not work like that in Germany in the 90s and 00s. Workers were persuaded not to go after raises, although profits soared, to avoid losing jobs to countries like Poland. The German government decided to keep the surplus from exports and indirectly brag about it, as if countries are households. The result of this idiotic policy was of course that German industry scored record profits, but wages remained stagnant for ~20 years since by not investing in infrastructure the govt kept wages low “virtually”. Then negative interest rates came, the EU went berserk and the AfD is the third political power in Germany. So much for the surplus.

Back to the matter at hand... having workers in the board helps, but doesn’t secure raises.
At least two of those points can arguably be greatly improved or avoided in MSRs. Since the reactor is not pressurized in an MSR, no large heavy forged pressure vessel is needed. And the steam cycle of a MSR can operate with supercritical steam w. reheat, like a conventional fossil plant's steam cycle, reducing the mass flow needed by as much as as factor of two.

The other big savings for an MSR is a very large reduction in the size of the containment building. This is because there isn't water in there that would turn to large volumes of steam during an accident and that would have to be contained by a large pressure-bearing structure. Moltex claims their containment would be a factor of five smaller per unit of power output, compared to a LWR. This would be a huge cost advantage.
I've had DSPS for my entire adult life and it has been incredibly difficult to manage. For me the biggest improvements have come with maintaining extremely strict sleep hygiene: F.lux or the equivalent on all my devices, setting a "start getting ready to go to bed" alarm on my smartwatch, generally avoiding caffeine and alcohol entirely, wearing blue blocking glasses when I'm going to bed, and maintaining the same bed time and wake up times even during the weekend. As well as using a light based alarm clock as my primary alarm. It can still be a challenge to be well rested but I do a vastly better job of it than I had previously. I don't always make it to work at the time I want but compared to the "bad old days" where I might come to work on only 3-4 hours of sleep one day and I might roll in at 1pm, 2pm, even 3pm some days it's like a quantum leap improvement.

The other major factor is getting regular exercise.
Ok now I'm just confused.
> just 2 of the 3 listed companies are major sponsors of OSM events

Don't assume that because a company isn't listed, it doesn't/hasn't contributed.
As others have pointed out, LEO satellites solve the latency problem. Why then was this not done before? Because LEO satellites move. You can't use a fixed antenna for LEO; you have to track the satellite. This means you have to use a motorized antenna (cumbersome and expensive and generally impractical) or use a phased array antenna with no moving parts. Only recently has the technology for phased array antennas become cheap enough for average consumers. So the delay in fixing the problem was mostly the fault of antenna technology rather than satellite technology.

Postscript: Iridium is LEO and doesn't require a fancy antenna. How come? Iridium is designed for voice; throughput is a few kbits/second. That's way too slow for modern internet. For mbit/sec speeds, you need a higher signal-to-noise ratio and an omni antenna like Iridium's won't cut it. You have to track the satellite.
Ask HN: Remote pentesting role for company?
How do you have effective communication with your mgr and/or ciso?
My more charitable reading of dtien's comment was that instead of society understanding that different people have different preferred behaviors and that some of those preferences are going to have a genetic reason for them, we end up creating pathologies for normal behavior with names like "Delayed Sleep Phase Syndrome". This name does sounds like it would come from a satirist, not the medical establishment.

The quotes around the word normal to me is the clearest indicator of dtien sympathetic view toward people with 'DSPS'. In a better world, people with late night preferences are just people, not labeled people with DSPS.
I wasn't familiar with SigOpt - this is really cool. I actually think SigOpt will see this as great publicity telling people about the usefulness of the concept - and whereas Google won't lift a finger for (insert hedge fund or pharmaceutical giant here) beyond maintaining uptime, SigOpt can provide those customers with customized advice about how to integrate, what pitfalls to watch for, how to design experiments to maximally take advantage of their technology.

And they're competitive with Spearmint (though not necessarily the closed-source versions of it used at Whetlab), though Vizier remains to be seen: https://arxiv.org/pdf/1603.09441.pdf
Tell HN: Braintree is no longer startup-friendly
About 3 years ago, after researching payment processing options, we chose Braintree. The thing is, they were still riding on the goodwill they had built up thus far pre-paypal purchase.

Paypal is a total nightmare for some people (especially if you plan on growing fast), so the fact that they were recently purchased by them, should have been a red flag, but customers and reviews still seemed positive.

One of the selling points with Braintree was always that once you are underwritten, they are going to work and grow with you. Unlike Paypal, who will arbitrarily freeze your funds at the most inopportune moment.

Apparently, Paypal has now applied this same policy at Braintree. One of the features we offer our customers is allowing them to sell event tickets through our software. They can use their own merchant account, but we encourage them to use our in house system (braintree marketplace) because it is usually faster and easier.

And so it worked fine for 3 years, slowly growing, processing more and more payments through more and more sub-merchants. Hundreds of thousands of dollars. Then they just decided to shut down 2 of our newest customers and hold 100% of their funds ransom for 180 days. More than $50k for a single customer which is a terrible burden. Reasons given was that we had a sudden increase in marketplace sales from this new customer and they don't want the exposure (even though we processed even more than this from a single sub-merchant last year in a short period of time).

So just wanted to put it out there that Braintree is now up to the old tricks of Paypal. Lull you in to a false sense of security, then lock up your funds suddenly for whatever reason with no recourse.

If you currently use Braintree, be careful, even with a good growth history on file with them, they are no longer startup friendly as they can't seem to handle spikes in activity or at least have no desire to do so.
In my opinion as someone present, this standard was met.

(1) Programmers need to be able to communicate about what they did, what they need to do, and how things are designed. (2) Interviewers kept on saying things like, "I managed to pick out enough of the right words that he probably answered me, but I wasn't sure."

None of us cared that he had an accent - we hired plenty of people with accents. We cared that we could not understand him well enough to coordinate with him. But if we had told him that, he would have had grounds to file a lawsuit. We'd have hopefully won, but he could still file it.
No I’m sure istedgade is a better fit for you.
What are the political implications of the entire world becoming so reliant on TSMC, with nearly all of its manufacturing concentrated in Taiwan?

It's no secret China is eyeing semiconductor manufacturing as sort of a last frontier they need to cross before they become a vertically integrated powerhouse. If China took over Taiwan, and assumed influence over TSMC, wouldn't this be a major achievement?

1. Why aren't TSMC scattering their fabs across different continents - not only for political, but also to protect against natural disasters etc?

2. How much of the USA protection of Taiwan takes into account semiconductor manufacturing?
serverless
There was an icecream advertisment with that as a theme.

https://www.youtube.com/watch?v=j4IFNKYmLa8
Why bother videorecording interviews at all?

We don't record interviews. By "remote video interviews" I meant "remote interviews by videoconferencing such as Skype or Google Hangouts" which I assumed was what you meant when you proposed candidates use their own office or couch.

why not just tell them ahead of time what their
environment needs to do when they get there?

We did this, including a github test project they could check out and build to make sure everything was working. Still, about 50% of candidates arrived without a working environment.

We chose to supply a known-good laptop instead of rejecting such candidates instantly when they've spent time travelling to us etc.

every time I hear someone explain how challenging or
untenable our process is, I keep wondering, "what am
I doing wrong to make this work so well for us?"

I'm not saying your process is challenging for _you_ given _your_ situation; I'm sure it works very well for you! I'm saying it's challenging for _us_ given _our_ situation :)
Okay. I get it. You're using the low-quality "alternative news" articles with clickbait headlines to draw in short attention span readers because those are your cash cows. Having that steady advertising income allows you to finance real journalism like the things you listed that might not be able to stand on their own in the current trend-or-die marketplace.

So let's make a deal. If I pay a subscription, will you only give me the good headlines and not spam me with the crappy stuff I don't want to see?
Not to mention publishing the Steele dossier
funny how I am reading this while trying to instill in my infant daughter the "conventional time" habit...

I am really left with doubts on whether it's better to support a baby's time schedule or to "force" the standard's.
Integrating LLVM requires quite a lot of mental effort (Let's not even discuss GCC...), whereas writing from scratch can be "simpler" mentally (at least to start with).
Agree this a smart move. They should be targeting lower volume markets where the 30% decrease in per-die cost at 7nm isn't offset by the increased upfront costs. If they focus instead on decreasing fixed costs of lower volume ASICs, they will have competitive advantage in long-tail markets.
How to start your own web hosting business
> Don't assume that because a company isn't listed, it doesn't/hasn't contributed.

That is the list of all sponsors for that particular event. Apple did speak at the event, though their talk[0] was the only one not recorded, photos were forbidden, and they uploaded no slides afterward. The topic was their employees' volunteerism.

[0] https://2018.stateofthemap.org/2018/T081-Working_with_the_Co...
Mostly it just appalls me that I habitually share space online with people who believe those things about women, being a woman myself. There are social contours of a space which dictate norms of behavior beyond explicit enforcement of rules, and I suppose I just assumed they were different here.
Do you have a source? I'd be interested to look at the work they're doing.
That's only technically true. The main C++ compilers in common use basically support, aim to support or have collectively agreed not to support parts of the C++ standard.
Those are actually already removed from the disengagement count if the operator can show (with simulation) that the car would have done the right thing without intervention.

If it didn't work this way you would be incentivizing operators to train their drivers to take risks in order to hit disengagement metrics which would be bad.
This goes both ways, and frankly it is racist to say you can't be bothered to try to understand someone's accent. I've worked with asian immigrants who learned english on the job, it's really not that hard to work with someone with a non-American accent.

And if the DSA in your name stands for what I think it does, you should know better.
How would you have handled a deaf candidate in the same position?
I read the related article about Postgres SELECTs causing writes sometimes - I've used Postgres for years and never knew this!

Anyway, I spend most of my time in the software world and occasionally have to setup hardware (or more commonly, diagnose hardware issues). Is there a good guide for how to setup things like Postgres or Redis with recommendations on swap/cache setup, RAID-level selection, etc?
I suspect our experiences differ, or maybe it's our philosophies. I'm of the opinion that if your self-tied knot bites you 3 years down the road, that's better than the status quo. :P

That's situational, of course. My current projects are tech giant things, so some choices actually do have a >3 year window, but then there's a tech giant sized stack of use cases to design against.

When my projects were startup problems though, I'd be happy if that component still worked well after 3 years of growing and pivoting. In that kind of environment, getting more for free is by itself valuable for your ability to pivot quickly.
Our traffic data is generated in house using anonymized location telemetry from our SDKs, much like most other traffic providers. The live speed predictions we generate for congestion and ETA models are competitive globally, providing the most accurate ETAs available in many parts of the world. Our accuracy today is particularly strong in the US, when compared to similar services.
> There's a very limited amount of competition that can operate when a city has to approve someone digging up the roads every time a new company pops up.

The solution to this is for the actual physical infrastructure that requires digging up roads to be owned by the city (or other local entity), so it only has to be put into place once, when the city is built; and for competing ISPs to either lease, say, fiber bandwidth from the city, or get a permit to pull their own cabling through already existing underground tunnels.

The problem is that every municipality that has tried this solution has been sued into oblivion by the ISPs, who want to prevent open competition by any means necessary.
>"Can't understand their accent" _is_ discriminatory. Please don't ever recommend against a candidate for that.

Sorry, I disagree.
A team is more than just a bunch of automatons punching the keyboard.

If I can't understand what you're telling me, if you can't communicate your ideas, if nobody can understand what you're saying, if everything needs to be explained multiple times, and/or slowly, it becomes exhausting to work with a person like that.
I have definitely seen people confuse them, although not in production code.