skysight-inc/HackerNews huggingface dataset:
>Ensure you are compensated appropriately.

I agree 100%

My last company is notorious for official-unofficial on call duties.

You must remain within 30 minutes of the office, be near your cell phone and sober, 24x7. Because there is no official policy, there was no rotation, so technically I was always on call. Their official stance on compensation is that salaried employees can't get overtime, and it's covered by the annual bonus anyway. Yep, unlimited on-call & overtime covered by a ~7% bonus that pays out about 50% of the time.

I was once out of the country on a statutory holiday and didn't answer my personal cell phone (roaming would have killed me), which caused me to get reprimanded and lose my bonus for the entire year.

After some back and forward I quit soon after.
Ask HN: What is required for a Danish citizen to work in the US for 6 months?
I have a friend from Denmark. He wants to come and work here as a software engineer in the US later this year, as a sort of intern, starting August or September, until his next university semester in February. I don't know a lot about this subject, but my first inclination was to explain to him that he can't work here without getting a company here to sponsor an H-1B visa for him. Firstly, is that true, or is there another way? Secondly, do you know of any companies that sponsor such pieces, or if there is an online resource for finding such companies?
[...] these gains in productivity are going more and more towards companies and investors (mostly thanks to the competition from Chinese laborers) instead of (western) non-elite workers.

This seems illogic to me - if you have to compete with cheap labour you have to cut your costs in one way or another, pay less to your work force, make them more efficient, accept smaller profits or what have you. Putting more money - in absolute terms - into the pockets of the capitalists only makes it harder for you to remain competitive. Therefore I could at best see that capitalists receive a larger share of the cake in relative terms but not in absolute terms due to competition with cheap labour.
> Well an IDE with less features is going to be faster than VS, that isn't a question. Just see Sublime Text, insanely fast until you start adding extensions and it gradually gets slower and slower.

In principle, only a small proportion of features need to be actively consuming cycles. Most require no resources until invoked by the user.

Only a small proportion of those features are actively involved with drawing and so need to block the UI thread sometimes.

And only a small proportion of those features perform some essential drawing operation and so need to block the UI thread every frame.

So while a badly designed IDE with fewer features will outperform a badly designed IDE with many features, both will be trounced by a well-designed IDE with many features. It's the design that matters.
> If a machine is compromised is a client cert really any better than a cookie?

I'd say that currently, it's actually worse. At least a cookie can be easily invalidated and regenerated, and typically expires after a relatively short time. Invalidating a cert is easy enough from the server side -- just stop accepting it. But how do you invalidate it and regenerate a new one on the client side? Well, currently, you ask the user to go into scary menus and do scary operations to delete the existing one. Then you can request the browser to generate a new one.

I think this is exactly the heart of the question that the article is asking. How do we make certificates a better form of authentication cookies?
One thing I like about Elm over the plethora of Javascript converters is that it is its own language devoted to one runtime (js) and a very different language than most (syntax wise). The same goes for Coffeescript as well.. for the most part at least.

I particularly don't like general purpose language to JS converters like Scala.js, Clojurescript, GWT, etc because I think these converters can cause some cognitive dissonance (based on past experiences). That is I actually think its better to have different languages for different environments but I suppose not everyone shares that belief.
Companies may be legally required to keep "work" chat logs: http://www.wsj.com/articles/deutsche-bank-didnt-archive-chat...
It seems like they've made the classic mistake with C++ parsers of reinventing the wheel. I have never used an IDE which is capable of correctly parsing all the C++ code I've used.

The notable exception is anything based on clang, which is usually flawless (as you would expect). If CLion had been based on clang then they would have saved themselves a lot of work and ended up with a better performing product. Presumably the reason they didn't had something to do with licensing.
Have you ever dream of your Apple gadget serving all your needs?
Will your product sink or swim? Look at your First Time User Experience
Police say they can crack BlackBerry PGP encrypted email
That fails because one of the explicit stipulations in the problem is: "The pirates do not trust each other, and will neither make nor honor any promises between pirates apart from a proposed distribution plan that gives a whole number of gold coins to each pirate."

I read that as "an actual proposal, by the leader" not as a "theoretical future proposal, iff that negotiator becomes the leader" and I believe that's the intended reading.

Thus, D and E cannot trust that you'll hold your word to give them 33 coins each provided you get to be in charge.
Show HN: Open-Source Speech Tech SDK- ESL Focus
interesting. are you also supporting mobile devices? any issues with iOS or Android to consider?

I am considering flexbox but have to worry about supporting above. Luckily we don't have legacy IE to worry about so am hopeful.

according to this [0] ie 10 and 11 are supported but with "partial support"?

[0] http://caniuse.com/#feat=flexbox
The only known mammalian prion is PrP, which noticeably affects animal behavior, and is detectable by testing lymph. If the animal has prion-related encephalopathy, you burn it.

Viruses cannot reproduce without living cells. Viruses that employ lipid capsids would likely be removed by the detergent along with the cells. Some viruses do embed in a type of extracellular matrix (HTLV-1). As far as I am aware, no research has been done on the transmissibility of viruses in decellularized animal organs from donor to recipient.

I presume that those facing imminent organ failure would rather catch a cold from a pig and recover in quarantine observation than die while waiting for such research to conclude.
How does this apply in BYOD scenarios?
Actually, if IE 10+ is the target for my site, I would totally use FlexBox. The list of workarounds is far shorter than CSS headaches used to be. Remember the terrible IE on Mac days? ;-)
Holy crap, I thought places like that only existed as straw mens in articles about bad practices. It'd unlikely that any other place would be worse, you have little to lose by changing jobs.

A company that behaves like that is actively trying to find ways to cut your job too and they will just as soon as they think they can get away with it... Or maybe they'll cut someone else and have you do their job too, for efficiency.
There will likely be a winner, or multiple winners today. If not, it'll be +EV to play in the next drawing, and might be already.

It's $2 * 292M, $584M minimum payout, for the odds to be in your favor. Expected payout is now up to $930 * (1 - 0.395), so $562M after federal taxes. Depends on state taxes, and if the estimate is a little low, only about $20M short this morning.
I'm not the GP, but I think I can answer for AFS. To this day, nothing has come along that handles the global-scale filesystem use case as well as AFS did way back when. What we have instead are these:

* Parallel filesystems that fall apart at more than a few ms latency.

* Geo-distributed filesystems that are too slow/insecure/unstable to be useful for anything that really matters.

* Ways to sync separate remote filesystems, but with no pretense of consistency.

* Things that don't satisfy even basic filesystem semantics (e.g. object stores).

* Things that are proprietary, and thus useless/irrelevant outside of their originating organizations (e.g. Google).

That's why there are still some very large installations of AFS or its lineal descendants; I know of one that's 50K+ machines. I once had a dream of creating such a successor, but have largely abandoned it. It's not that the technical challenges aren't both interesting and solvable. It's more that the financial, logistical, and personnel aspects of getting such a difficult project completed and used by anyone would drown out all of the fun. I know a few others who have reached the same conclusion, sometimes up front and sometimes after losing years to the effort.

The only way such a thing will ever get done is if some deep-pockets org needs it enough to fund and support its development, while also being fully committed to open source. Unfortunately, every org with such capability seems satisfied with one of the alternatives mentioned above.
Too often I see startups who fail to realize their potential because...

Product owners forget the importance of the First-Time User Experience (THE FUX). Products must deliver immediate value to new users; the FUX is the key to activating, then retaining users. A FUX that disappoints (not the same as onboarding) can halt your product in its tracks, whereas a FUX that exceeds expectations can accelerate your product's growth.

I'm building a tool with dscout that delivers videos of people discussing whether the FUX lives up to expectations, where each new user rates your product before using it, then after using it. These two ratings enable you to compare user expectations of your product to their actual experience, and the videos tell you why.

I'd love some feedback on this new product and our approach to measuring expectations!
Show HN: Seamless remote networking for developers
Hello HN,

I see lots of developers spending time away from coding because they have to deal with complex VPN deployments to securely access their servers, or to connect two or more of their locations.

I thought it would be great if someone could take that burden away from you, so you don't have to think about VPNs, firewalls, opening ports or risking having a wide-open server. It would actually be really great if you just had to spend less than 10 minutes to have a bunch of remotely located VMs sharing a local network, especially if the traffic between them was encrypted. This could potentially unlock new architectures where you could have the frontend, backend and DB servers located in different hosting providers - in a transparent way for your application.

The main caveat is added latency, as this solution requires one extra hop; but by carefully placing my servers close to the users' resources this can be severely mitigated. I'm on my first iteration of the product, running on a bunch of servers on Digital Ocean, but as more users join and start using the system I'll be able to identify better your needs and adapt the service.

The service is built on top of SoftEther, a well-known open source VPN software. The software hasn't been modified a single bit. I've just built a management system around it, provided servers with a very specific configuration and tried to make the user experience smoother.

There's a free tier on shared (and tiny) servers so you can try how easy it is to make it work. No credit card needed and no time restrictions on the free tier.

The link is https://wormhole.network
Digital is clearly the winner here from various perspectives but a bit fragile, but if we had to pick something that was especially solid and apocalypse proof, stone tablets would beat out print any day. Newspapers and books decay relatively quickly, are susceptible to fire, susceptible to flooding, etc. You can go to London and read the 2200 year old Rosetta Stone all you like after learning the basics of ancient Greek (like I did), which shouldn't be too tough for a native english speaker. Or if you're a real go-getter you can learn ancient Egyptian hieroglyphics and read the pottery from Abydos which is about 5200 years old. Meanwhile, we just have to accept the losses at the famous burning of the library of Alexandria.

Newspapers just decades old are all but dust now. There's no lasting power in paper. Stone and clay tablets is where its at. From a more realistic perspective, we live in an age where every tinpot dictator can get nuclear weapons and every powerful nation has enough to end the world, so past ideas of human survival let alone knowledge survival may be a bit naive. There's probably nothing that will survive WWIII and there's no reason to think WWIII isn't going to happen eventually.
Making a deal like you propose is explicitly forbidden by the rules. Or more accurately, pirates don't trust each other and will not honor any deals beyond the current split proposal. Of course, pirates in real life wouldn't behave like this, but these are not real-life pirates.
A new approach to Function.prototype.bind
Well, do you have hobbies? Interests? Things that you think about wanted to do when you're at work? Things you have to stop doing because gosh darnit you need to get up for work tomorrow even though you'd rather carry on until morning? If you have those, then why not do them more?

All those things you enjoy and do without question or thought, or wanted to try, those are the things that you do.
There's a list of bugs, test cases and workarounds here: https://github.com/philipwalton/flexbugs

One bug used to affect non-IE browsers but should now be fixed in all but Safari.
You can't. You won't know until you're in the role.

Source: ~15 years in the tech sector
How much time do you have? The rule book is like 600-700 pages. The best route I recommend is to engage your bank or processor, like Dwolla or Stripe, with your use case. They should be able to quickly identify what the requirements are for your platform.
The new retail battleground: Combining identity management with privacy
This would make a good "Show HN".
I don't follow either. In addition to what you say, the rules state that, all else being equal, pirates would prefer other pirates to die. Pirates would prefer A to die, so they would vote against this proposal.
Use data with a smaller size N, and do something more interesting with it.
I suspect a lot of the creative uses of C++ in Qt will fade over time as C++11/14/17 support in compilers improves. There are more options in the language now that would allow the project to move away from so many macros, etc.
Experts aren't entirely sure why "those who can least afford it play the most," as German sociologists asked in a 2013 paper. The pessimistic, and perhaps condescending, view is that the poor and less-educated don't have the intellectual gifts to appraise the odds, but middle-class and rich people play the lottery too.

This perspective is deeply flawed. If humans obeyed a risk adjusted rate of return strategy and rationally discounted for the future, human behavior across the board would be profoundly different. The lottery is only one example of many.

Any portfolio of early stage startups is destined to perform worse than the S&P500, as is any portfolio of series A startups. As is any portfolio of lottery tickets... but there is always that winning ticket, that Facebook, that Google.

There have been very few big homerun startups. The rest would fail to lift the average above the S&P.

In an environment where the future seems fairly certain (poverty, affluence, whatever) there is lots to be gained by rolling the dice and experiencing a bit of risk. Lotto is less fun than a startup, but it scratches the same itch. It lets you ride the emotional roller coaster and imagine the greatness that will one day be yours.

Startups are a superior version of lotto because you get to be the CEO or the CTO and someone invests their money to help you build a team and get traction, etc. So your bet with destiny is being underwritten by others. You get advisors, board members, and metrics, and essentially spread the thrill of the tumbling balls across however long your runway lasts. The superiority of startups is why young affluent people do them, and why poor people play lotto.

The urge to take on risk is what got humans onto ships, rockets, and bathyspheres. It's the unique human ability to reason probabilistically and take a leap, to undertake a calculated risk, and to engage in an exciting dance with destiny.

For centuries and in pre-enlightenment times, people believed that all of life was fated and that one's lot was destined from birth.

When we appreciate the emotional thrill of risk we start to see that it's part of the glorious awakening of the human sprit birthed in the enlightenment. When a dejected person puts his last quarter into a slot machine, we are not seeing hopelessness, we are seeing hope in its most unfettered form. Even if he loses that person will pick himself up and dust off and be ready to try again, for fate is on his side. This stands in stark contrast with the previous worldview in which the quarter would be saved and a prayer offered up, which has far smaller odds of success than the slot machine.
So many red flags, time to find a new job. The big one I recognize from a previous job is the 2AM feature implementation. In our shop it generally went like this:

* Sales, having trouble closing a sale, promises a non-existent feature

* Customer tries to use imaginary feature, calls sales to complain

* Developers have to drop what they're doing and implement imaginary feature full steam

edit: formatting
You'll still need floats to text and images, but this takes care of quite a bit any float based layouts
It's never positive EV, once you account for taxes and the odds of multiple winners.

It may, of course, have positive utility.
Minimizing 2am issues, and maintaining an on-call rotation, aren't contradictory. There's no substitute for having someone on call; but you can minimize the number of times they actually get called. This topic is near and dear to my heart.

You talk about testing - that's one side of the coin; the other side is careful alert tuning, (a) to minimize false positives at 2 AM, (b) to catch incipient issues while it's still business hours. (It's useful to think of alerts as just another phase of QA - the one that occurs after you hit production. The sooner you notice a problem, the less damage it causes, to both your customers and your sleep schedule.)

At my workplace, we run a fairly complex system, but we've been able to keep nighttime pager incidents down to I think less than once per quarter, including false alarms. I can't remember the last one. The QA effort isn't overwhelming, either. See http://blog.scalyr.com/2014/08/99-99-uptime-9-5-schedule/ if you're interested.
And 58% end in death - what is your point?
Has your buffering got any back-pressure at all? Or do you buffer until the disk is full?
Why is the latest AMD hardware unsupported in libreboot?
Call Pest Control: The Bug Problem at the US Embassy in Moscow
Its not horribly broken, IE11/10 is well supported with prefixes & past flexbox-spec properties. Autoprefixer does all the work there. For IE9/8 you could rely on polyfills like https://github.com/10up/flexibility

Listened to @_lemonmade & @snookca at a recent conference talk about how they're using Flexbox across the Shopify platform and there is no reason why other far-reaching platforms shouldn't make the switch today.
Know Before You Go: Ulaanbaatar
Gressing
Funny thing here inn my urban district, my daughter's 4th grade class had their FIRST Science class this school year on Tuesday. I think it was because she kept asking the teacher to please teach it.

How about our kids learn 5 subjects not just Reading and Math and give them opportunity to learn Computer Science (Its Business apps here sadly).
I would define the term "high-level language" to mean that it's possible to write programs in the language without needing to worry about the specific hardware that the program is running on.

I would consider systems programming to be things like writing operating systems, drivers, high-performance native applications (for many difference definitions of high-performance), and databases.

I consider rust to be a high-level language and I further consider it to be suitable for systems programming using my definitions.

However, I don't consider go to be suitable for a lot of systems programming tasks because it has a significant runtime system that includes a garbage collector. Just because they describe themselves as a "systems programming language" doesn't mean that I believe them (at least as far as I understand that term). That said, there are certain applications that work fine with GC, and in those cases it can be a very nice way to achieve memory safety without programmer burden.
One of the web's greatest features is progressive enhancement. So you can (and in my opinion should) use flexbox now as it has pretty decent browser support -- just make sure there is a decent fallback to something that is not-as-visually-perfect-but-still-decent (such as ye old float-based layout or display:table).
> If they didn't, and he is simply personal making accounts using the corporate network, then he would not have an expectation of privacy in my opinion.

Not quite right - this is one of the grey areas where the law defines something in between "has an expectation of privacy" and "doesn't have an expectation of privacy". Basically, the employer generally can't access personal information on work computers, even connected to work networks, unless they have a reasonable belief that e.g. there's evidence of the employee breaking policy in that personal information.

Even then, they must access as little as possible - for example, if you believe that the employee has personal information on their computer and having personal information is against policy in itself, and that's the only thing you believe, all you can do is ascertain that it actually exists - you can't go digging through people's family photos or private communications unless you reasonably believe that there's further policy violation in there.
Not quite, I think.

I've been using it, it's cool and all, solves some common CSS issues, but it comes with its own set of problems. For starters, it's a whole new set of browser incompatibilities that you have to learn [1], some of them render flexbox almost useless [2]. Additionally, IMHO, it's model is leaky; leaky in the sense that the it relies on DOM structure - a `display: flex` element will do it's thing by affecting the direct child elements. This means that a) if your component is wrapped by another component, you'll have a hard time predicting how it will be laid out/isolating the behavior; and b) if, by some reason (e.g. using Angular directives) a wrapper is added between the `display: flex` and the flex item elements, the layout will be lost.

[1] https://github.com/philipwalton/flexbugs

[2] https://code.google.com/p/chromium/issues/detail?id=346275
I am one of those people good at mental math - enough that our founders turn to me in meetings - and I think it's useful.

Instead of thinking of it as a skill, think of it as an exercise.

There are hundreds if not thousands of things trying to distract, mollify, enrage, and lull us into a "don't think, just act" attitude... having mental fortitude to counteract or ignore those is important.
> You do realize that concentration camps had been up and running since 1933, right?

You realize the camps were not exterminating people until after the Wannsee Conference in January of 1942, right? That isn't to say the Nazis weren't murdering people before then, but mass murders didn't start until the war started and were generally committed by the Einsatzkommando units in the field. As for the racial policies of the Nazi Party, there was a disturbing amount of support for them outside of Germany prior to the war.

Still, Nazi metaphors are almost always an unnecessary hyperbole.