skysight-inc/HackerNews huggingface dataset:
This is going to be a massive thread I predict. There's a big world out there. If you can't afford California, or you don't want a 2 hour commute with a $180,000 salary, then DO NOT LIVE THERE. It's that simple. Are you skilled, and you can't afford or don't want to afford to live in California? Give up the damn weather and move somewhere else. I don't even care if it's because the laws cause unaffordable housing, just don't live there. Besides, if you drop the housing prices so much that anybody can afford to live in California, how great do you think it's going to be there? The issue with a place like California is that there are almost always going to be more people that want to live there, than there is space. If you build more/better/affordable housing, more people will move there, then what?
This seems like a Rube Goldberg solution for a problem better solved by just... not using a SPA for a page with the primary function of displaying text.

I mean, maybe I'm missing something. What's an example of a page where this would be useful where an SPA isn't vast overkill over just sending HTML to the client in the first place?
I was working on a control system for cattle feed mills. We had to wire into the system sensor-by-sensor and actuator-by-actuator as they continued to make feed. We started out with the entire system simulated, then gradually ended up with a fully live system.

I (thought I) set an actuator running an auger (screw) that offloaded the feed from the mixer into a leg (12 meter tall vertical screw) to "run always." That should be safe right? The auger runs all the time, carrying away anything that dumps into it. What I had actually done was set a hay belt to "run always" it was stuffing the mixer with more and more hay until it was a solid mass inside the box.

Everything seemed fine when we started that next batch of feed... then the mixer started. The lights dimmed and there was this shriek of metal and a bang from the mill floor. We shut down and went out to see this huge mixer hanging off a drive chain at 45 degree angle from the floor. Bolt heads the size of manhole covers had sheared off and were lying nearby. Fortunately no one had been standing nearby. I don't know if my memory matches reality, but I recall a light from one of skylights shining down on it in the grain dust like a spotlight.

I was pretty sure this was going to be my last day on the job.

I walked over to stand next to the Mill Manager, a salty fellow named Marvin with three fingers on his right hand. Marvin looked up the chain and back down to the bolts on the floor and said "Yep, it'll do that."

Two workers lowered it down and welded the bolt heads back in place like they did it every day.

I was with the company for five years. I don't recall every having a support call from that mill after we finished the installation.
Nice, I loved Freespace and Freespace 2 - but haven't looked at the mods.

I'm currently into Star Citizen, Elite Dangerous, and have also backed http://starfighterinc.gamepedia.com/Starfighter_Inc_Wiki which looks really promising. Oh and Eve-Online, however that's not first person as such.
Thanks for the link to this interesting paper.

I think we're seeing some recapitulation of those arguments WRT 'ensembles of DL models' approaches.
I lost my father at 15 to his work. He had a relatively dangerous job, made a mistake, and it killed him.

This was 4 years after I lost my mother doing something she was passionate about.

I can tell you in no uncertain terms that losing both parents before you turn 16 is no walk in the park. But I managed, I survived, and now work in a field that often touches both of the things that killed my parents and I have a bit of a desire to 'conquer' the things that took them.

I wish they both were here today, but I do not wish they hadn't done the things they had done. Even as a kid I held no ill will toward either of them. I'm glad my mother got to do what she wanted, and I wouldn't be where I am now if it weren't for my father's line of work.

I am not a biological father and I have gone cavern diving. While it's not okay to be reckless and disregard all safety, as a child of parents who passed doing unnecessarily dangerous things, I can say that I have never wished that they had not done those things that they wanted or felt necessary to do. I only wish that I had made better use of my time with them.
High rise housing projects take many years. Just assembling a suitable parcel in a good location from multiple small parcels under separate ownership requires cunning and misdirection and often a couple of decades.

Real estate is slow. Apple has its new spaceship in Cupertino. Apple paid $300 million for HP's 100 acre former campus in 2010. Apple's adjacent parcel was acquired in 2006. Even without regarding how long it probably took to close the first parcel, that's more than a decade ago. For a straight up office building with no need for sales and marketing. And office buildings are what Cupertino wants on its tax rolls.

Suppose that 100 acres went to housing instead. At $3million per acre and 30 units gross per acre, there's $100,000 per unit in land cost. At a low end 4:1 improvement to land cost ratio, the construction of each unit runs out to $400,000 and the unit cost is $500,000. Throw in 20% for carrying costs and 20% for developer profit and units hit the market at $720,000.

Sure a person can play with the numbers and get them lower or higher. But even at 30 dwelling units per acre, that's only an addition of only 3000 units over ten years to the overall Bay Area market. And it took more than $1 billion in capital and a decade worth of work. If it were easy, it would have happened.
"All fat with a tiny smidgen of protein" is an interesting way of describing egg yolks and olive oil. (Not saying that Helleman's is anything more than soybean oil and 3% egg solids, though.)
There's also the mundane question of money. Unless you're already rich, raising a child alone is hard in many counts already; having your income halved does not help.
Marketing AI Driving with an Emotional Connection
Really hoping there's at least one Ariane 5 avionics engineer who reads HN...
Smart Wallet
Hi Guys,

Long time lerker, first time poster!

Scrolling through indiegogo, I found something called the Thorne Smart Wallet. Everything from lights to dishwashers nowadays seems to be smart, but didn’t expect a wallet to be smart!

It seems quite useful for me combining my wallet with a powerbank and storage. Just wondering what you guys think and whether its worth crowdfunding?

On further research I've found another on indiegogo thats been launched for a few weeks now, but seems to be getting criticized a lot on sh*ykickstarters on reddit. Which if any would you buy, and do you think smart wallets are the future?

Thanks guys and hope to not lerk as much from now on!

https://www.indiegogo.com/projects/thorne-wallet-smartest-power-wallet-wifi-smart/x/17019121#/
Some of these comments were left by my friends, so I can say that these are real people who are in the topic or are interested, but they are just laconic and restrained in their assessments)
Trump was born rich, and like people who were deemed old money in the 1920s treats tech's new money as not very important and not worthy of attention.
I wouldn't pay much attention to it, because it's probably the last hoorah before the death of the old economy.

In the end it'll be a short lived moment in history until this generation's kids treat the next generation with similar disdain.
The Rise, Fall and Rise of the Rubik's Cube
This looks amazing.

And... I keep waiting for MS to provide an add-in to Excel that will allow ML analysis and similar visualization.

Even better, someone beat MS to it and do one for Libre Calc.
I wrote some code that was pulling batches of events off a queue, doing some processing and then writing them out to HDFS.

The inner loop was something like:

while message:
converted_event = new Event()
for event in message.events():
converted_event.set_fields(event)
write_to_hdfs(converted_event)

Can you spot the bug? Led to a month of corrupted data before I noticed..

The `set_fields` method does not clear all fields, so every event had more and more junk data than the one before it. All because i thought i would be clever and get some performance gains by initializing `converted_event` outside the inner loop.
Yeah. I made something similar with a raspberry pi I had around the house. Hosted a simple HTTP Server using 10 lines of Flask, and used IFTTT's Maker service to glue it all together.

There are many ways of getting this setup, whatever you're most comfortable with. The key here is that this Maker service exists that let's you do basic REST input/output
A similar PLC story: A friend was an intern at a well known coffee manufacturer. He was writing code for new sensors to use which were to be installed on the assembly line machines later that year. There was a staging machine that his team used in the same room, and they would log into the machine and push their code to run tests.

He sent the machine an update, rebooted it, yet the staging machine was acting unchanged from the previous version. Moments later a supervisor ran into the room, yelled to put his hands up from the keyboard, reached over him, ran some commands, and disappeared into another room. A few minutes later he announced that my friend logged into the main assembly line machines and rebooted them with code that used a sensor that didn't exist yet, which stopped the entire chain for ~20 minutes. The company suffered $250k production losses during that time.
Since you are redesigning UI features, are there any plans for a site-native dark theme? Seeing as there already multiple code themes available, it seems within the context of the configurable UI part of the goal. There have been Stylish themes for gitlab in the past but they break a lot because gitlab is a very large website to try restyling from the outside.

Solarized-dark with a white frame can be quite grating on the eyes.
Depends on the kid, their age and their relationship with their father. I don't think there is any right generalized answer.

With my kids I know they would rather have me around, but they are young so I'm already "superman" to them. Who knows how our relationship will change as they grow older.
And the 3rd name is backwards. It ought to be called 'Linux Subsystem for Windows'.
Google must be broken up.
The capital investment required to make music these days essentially negligible unless your heart is set on setting up a studio so you can have a band like it's the 1980s.
What's the alternative to San Diego or San Francisco if you are in Pharma? Boston? You really need to live in a hub city, nowadays everyone changes employers every two years.

Wouldn't it be nice of we could go back to the old times, and there was a choice between Philly, the New Jersey pharma cluster, Kodak in Rochester, Solvay in Syracuse, Dow in Midland, MI, Upjohn in Kalamazoo and many more?
Study links artificial sweeteners and weight gain
A year behind the times.

https://trends.google.com/trends/explore?date=today%205-y&q=...
system("rm -rf $dir/")

I forgot to check my inputs. Ran in production for a backup system.
We have to be careful to identify genuine sexist behavior, and call it out, but also acknowledge that not every bad experience for a woman is based on sexism. Not every bad experience for a gay man is because of homophobia.

I have worked as a programmer for 25 years and I can assure every woman out there that men often treat other men very badly. I have seen programmers go ape shit because someone changed their code. Deliberately criticize another's work in front of a group in order to undermine them. Men play politics and undercut other men to boost their own reputation and career chances.

Some of the twitter comments identify sexist situations but some look to me like a man being a douche for reasons that might have nothing to do with sexism. We do not want to develop a culture where any comment to a woman/gay is always interpreted as sexism/homophobia. Let's not allow the pendulum to swing from one extreme to the other.
Dying at your hobby is #1 form of neglect, partly mitigated only if you've set up quite an insurance payout.
Are you aware of who any of the people are? Do you know anything about them? Seems like that would be relevant to your sneering comment there....
WebRTC badly needs interop with the official Bittorrent protocol. It's a neat API for now, but doing this would allow web clients to take advantage of the massive seedbox infrastructure already out there, making it actually useful.
Halide has some interesting ideas for image processing -especially regarding algorithm separation and scheduling - so great to hear its on your radar and be very interested to see what you come up with. My interest/focus is more on stencil codes and that is certainly an area I hope to test with DCompute. Congrats again (and thanks again) for an awesome project.
Why you should get to know Symfony in 2017
what are the actual measured chances of dying at these various activities?
Why does the price matter? I recently bought a house. There was "opportunity" in a "up and coming areas." It might have had up sides, but I didn't want the risk either. If the house price goes up I won't realize any of the gains until I sell it. That's likely going into another house. If the market moves as a whole then the price doesn't really matter (it would make "upgrading" more expensive). So I'm not worried about short term fluctuations in price. I, honestly, just want the price to stay the same.
I like the idea of triggering home automation just by connecting to the network. What's the status on that part of the project?
That's an application and not a patent. It probably will get rejected under § 101 as an ineligible abstract idea similar to Alice. Enfish won't save it.

Alice was decided June 19, 2014 and this was filed Oct 30, 2014. I suppose Goldman Sachs can take a flier; they have the money. But I don't think this will issue and GS should have known this then.
Then submit a pull request. Don't sob about it here.
The specific issue that we encountered was that the power was measured correctly, but was out of control. At that point, not being able to kill the power is a very real concern.

If we measured wrong, we could either be high or low. If we measured high (that is, the reading is higher than reality), we would either turn down the power until it read right, or else kill power completely. If we read low, though, IIRC we would limit how high we'd turn up the gain to try to get the power we were asking for.

There was also a feedback loop based on temperature. If the power was double what we asked for, the temperature would quickly climb, and we'd reduce power. It would have worked, even with inaccurate power readings, though not as smoothly as it should with accurate power readings. But when we got 20 times the power we asked for (due to the power control failure), it was too much too fast.
If you could make a self-hosted Jenkins replacement that is even half as good as Jenkins (think extensions) but written in not Java, I think it'd receive a lot of positive reception.

The trick with CI, like task/project management software, is that people don't look at what works. They don't try and compete on intrinsics like stablility, extensibility, etc, and really after 12 months on any platform, any mid-large size company is going to care more about those things than new shiny.

Jenkins had the absolute worst UI for a long time, and it still was many people's top choice for CI. You're generally writing a tool for programmers, after all.
>nowadays everyone changes employers every two years

They don't but, yes, there's a lot of clustering for various industries and industry sub-segments. I expect Kendall Square in Cambridge is bigger than most other pharma centers these days though.
still not a bad alternative to localbitcoins.com, you could arrange to exchange cash in person or mail money orders around which could still be cancelled if the escrow fails.
But money for the recruiter and freelancer comes out of a different bucket.

/s
My code probably contributed to the financial crash of 2007/8.

Unfortunately, I cannot share much details except that I wrote code that was meant to manage the amount of risk that a certain really big financial institution was supposed to take. My code may or may not have shipped after I left that institution. If it did ship, maybe it did not do what it was supposed to do. If it did not ship, maybe it failed to replace the broken system that it was supposed to replace. Either way, months after I left, the head of the institution acknowledged on TV that they were taking on more risk that they intended to.
It makes me feel nauseous just thinking about it, just the fakeness of it all. And we have to do it to survive. Holden Caulfield irritation of "phoneys" comes to mind.
On the last project I was working on, I built a backend on Node.js v4 for an online course site. For a long time I was trying to convince our team leader to switch to Node v6, since it supported ES6 and I couldn't wait to use the new JavaScript features like, e.g. classes. However, he was always reluctant to make the switch, since there were other priorities at the time.

At some point, I found out that inserting 'use strict' at the beginning of each Node.js module, enabled the experimental ES6 (harmony) features in Node v4. Needless to say, I was super excited and immediately started using classes and other ES6 goodies everywhere, even refactoring already existing modules.

Shorty after that, we noticed that our servers were leaking memory and started crashing almost every day. At the time, I had no idea what the problem was - and believe me I tried everything to find a solution - until a couple of months later we switched to Node v6, and everything miraculously returned back to normal. In the meantime though, during those 2 dreadful months between v4 and v6, we had to setup cron to restart our servers every single day at 04:00...

Never use experimental features.
Also some people just do not like coding in rust and that combined with the fact that its new means they refuse to switch.
http://www.insuranceclarity.com/life/life-insurance-extreme-...

OP is between "extra premium" and "cannot get coverage"
> If you can't afford California, or you don't want a 2 hour commute with a $180,000 salary, then DO NOT LIVE THERE. It's that simple.

This is great advice, it really is that simple. You have very little voice in California but you have plenty of exit.

> The issue with a place like California is that there are almost always going to be more people that want to live there, than there is space.

This doesn't seem quite as obviously true to me. While there's lots of people who want to live in California, along with all it's other bountiful resources California has a lot of space. We could, in theory, house many more millions of people before we really started hitting true space limits. It's not infinite of course, but the resources are very underutilized right now. Or at least they appear to be to my eyes.
Almost got me fired on the spot.

One of my first implementations at a bank many years ago... bunch of 'C' levels are in the main branch for my first big launch demo...

Tape a few keys...

**ERR ** HELL FROZE OVER!

LPT: never use this in an else case.
Been unused and irrelevant.
Win 10 virtualization available from Microsoft cloud partners starting this Fall
It looks like Emacs rather than Unix.
Kinda. And then the plant-based section of it. It is in line with what mankind supposedly really mostly ate for 100000s years.

The docu "What the Health" also discusses this diet and some other stuff.
1. Commute

2. Cost of living

3. Income potential

Pick two. Like everyone else, everyone wants everything. There's no place on Earth that has a short commute, low cost of living and amazing income potential. Compromise is the name of the game. Public transportation can help, but even still you'll have a commute. The only solace there is that you can do other things while you commute.

It'll be very interesting if commutes become on average 1.5+ hours each way and employers count time spent working while commuting.
Open-Source Neural Net Style Transfer
Google’s Quantum Computing Push Opens New Front in Cloud Battle
Not me, but https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/commi...
While I generally support the legislation discussed in this article, I wish the YIMBY people would stop talking about this in such simplistic terms. In some parts of California (e.g. San Francisco's eastern, urbanized third), no amount of building will ever satisfy the need, because all you can build on expensive land is "luxury" housing, and when those units don't sell/rent, developers will just stop building, because the unit economics don't work out.

Some places definitely need to build more housing -- see, for example, the western 2/3rds of San Francisco, or the cutesy little suburban enclaves of Silicon Valley -- but this won't help until transit allows people to commute from those neighborhoods to their jobs. So we should also be saying "YIMBY" to transit infrastructure and reducing/eliminating the broken tax incentives that are helping to create the problem in the first place (like the ill-conceived Mid-Market tax incentives, which have replaced SROs with tech offices, thus making the homelessness problem worse.)
California has been popular for various reasons for a long time. But it's really since the recovery from dot-bomb that things have gotten out of control.

Zoning etc. is part of the issue. But by all accounts, the (not so great) public transit--especially in SF itself--is pretty near capacity as, obviously are the highways. Can this capacity be increased over the timeframe of a couple decades? Probably. But there's nothing in the 5-10 year horizon that's going to make a [EDIT: not so big] difference other than a combination of people choosing to not live there, incremental housing construction, incremental public transit improvements, and incremental increases in congestion.
the people who die in war aren't the people who decide to get into a war.
From the data it looks to me like established community members were interested in the topic. Perhaps they didn't look at the article, perhaps they noticed something about it that you didn't, and/or perhaps they're familiar with gnocchi's fine submission history.
This is really unfair, it turns out that you are teaching that you just need to silently deceive, although it really was real people.
Yup and maybe I had incredibly low expectations but fedora 26 isn't bad either. Still wish I had a desktop or a business class laptop though.

Oh and I've given up on anything named one drive forever. The time am can't be trusted with anything worth anything.
risk is easy to calculate. reward is not.
I disagree here. You're dangerous until you know you know what you're doing. Having a bad scare might make you not repeat that situation, but you're still just as dumb after it as you were before (well, at least that's been true for me).
Especially when you think of services like Netflix, Spotify, and online games which deliver lots of bytes that definitely don't originate from Google. Without these services, this must be closer to 1/2.
New Customer Support Role Now Available
Kinda sloppy reporting. It's a meta-review (looking at past studies, no new data); only 7 of 37 were controlled trials.

Paper is here:

http://www.cmaj.ca/content/189/28/E929.full#T3

It looks like a slapdash grep for sweetener names as search terms; it doesn't distinguish one from another or see how many (or even which) artificial sweeteners were studied.

It's also disappointing that they didn't study the effect of AS on the microbiome, which is where I suspect the real mechanism of action lies.
We are so glad to hear that!