skysight-inc/HackerNews huggingface dataset:
Yep. Education isnt the goal, menial job placement is. Its cynical, but also true, that an educated populous would grind America to a halt, because we're reliant on people doing a lot of menial jobs... and educated people dont do those jobs...
> Hurricanes [...] tend to have much smaller impacts than earthquakes.

Then why are there so many more tropical cyclones in the list of most deadly US disasters than there are earthquakes?

https://en.m.wikipedia.org/wiki/List_of_disasters_in_the_Uni...

And why are the ten costliest, by insured losses: 6 hurricanes, 2 other weather events, 9/11, and the Northridge earthquake?

http://www.propertycasualty360.com/2016/04/26/here-are-the-1...
On one thread, I am defending FP from critics who are unaware from the state of the art.

EDIT: Just to make it clear early on, I agree with the article's conclusion that Nodejs is not as good at compute heavy workloads as Haskell. I simply object to any use of "the nested callback problem" as valid in 2016. It's an issue exclusively for legacy code and developers who take pride in writing outdated code.

It seems only fair, then that I also should defend Javascript from people obviously unaware of the state of the art in pseudo-imperative programming. And by state of the art, I mean "has been around in some languages for 3+ years."

The example:

request('http://example.com/random-number', function(error, response1, body) {
request('http://example.com/random-number', function(error, response2, body) {
request('http://example.com/random-number', function(error, response3, body) {
...
});
});
});

But modern Javascript (before you start, yes, it runs on every browser with preprocessing, which is normal for this ecosystem) would make it look more like this:

// rp is a request promise, multiple options for creating them
async function make3StaticRequests() {
try {
var res1 = await rp('http://example.com/random-number')
var res2 = await rp('http://example.com/random-number')
var res3 = await rp('http://example.com/random-number')
// ...
}
catch(error) {
// ...
}
}

// And of course the promise library allows for many things
// you'd like with applicative functors, like binding groups
// of operations together and evaluating them all.

function randomNumberPromise() {
rp('http://example.com/random-number')
}

async function make3StaticRequests() {
var [res1, res2, res3] = Promise.all([randomNumberPromise(),
randomNumberPromise(),
randomNumberPromise()])
// ...
}

I don't really understand why people feel comfortable writing up comparison articles without doing sufficient research into what they're comparing things to.

That said, the articles point about large compute workloads starving other operations is very much true and a good example of what the weakness of V8 as a server-side programming environment brings.
Kent Beck brought developer testing to prominence in the early 2000's with his books on XP and particularly TDD.

Back in those days, there was a backlash against "big design up front", and very little respect (in general) for testing as a practice. Unit testing in it's modern form was reasonably rare.

After this Agile/TDD stuff caught on, many people ended up over-testing things. This is a pretty typical thing to do when you're learning about how much testing is sufficient. I've definitely done a good amount of this myself.

It can take a good deal of experience to know where to draw the testing lines in particular contexts. I think this blog post points at this specifically - that we should write high-value tests, and just enough of them. We also use feedback over the long-term to have heuristics of where we tend to have recurrent issues, so we can test a bit more in those areas.

Far from being focussed on "only shipping", he's underlining the fact that "just enough well-written tests" support working software - and that should be our focus, instead of thinking our job is to "write more tests" (or focus on test coverage, etc).
That's not unusual. The media often portrays things very differently from the actual issues, as your example shows. Part of the problem is that media (particularly TV) has to keep people's attention, therefore it's necessarily in their best interest to sensationalize and simplify.

To answer your question, yes, the Supreme Court's oral argument audio is always posted online.
This was the question I wanted answered as soon as the article quoted specific texts.

It's possible that these things weren't monitored, but were disclosed as part of the suit. Even so, I'm a bit surprised that an exchange like this was retained at all, rather than run through an encrypted texting app and the history regularly deleted. It's one of those stories where the existence of the records is at least as surprising as their contents.
"Maybe it's just my privilege showing, I don't know"

This is part true, and is partly your morals and outlook on life.

The truth is that if you need the money, it is harder to enforce those boundaries or to fight against them. This is why more people can't have blue hair or visible tattoos: It can get you suspended, fired, or make you un-hireable. It is why some of the health insurance incentives really aren't a choice if you can't afford the extra 40% premium from your employer. It is why some folks can't avoid pre-employment drug tests (or random ones at work) on purely moral grounds.

But once you get past some of the crappy money ranges, not taking some of this stuff proves life outlook. You can choose not to work for the prestigious company because you disagree with their methods. And so on.
Let's quickly interpret this to further our pre-existing agenda (healthcare, guns, environment, vaccination, inequality, obama, immigration...)
Oyez does this for all cases. They also publish the oral arguments (which the Supreme Court itself releases) as a podcast feed, which I highly recommend. It's great listening even if you're not legally trained.

scotusblog.com also blogs about every case.
>>LinkedIn identity and network in Microsoft Outlook and the Office suite

Oh, gods. Please no. : [
You mean like in Cryptonomicon? ;-)
Test how mobile-friendly your site is with Google
My primary e-mail is hosted by a small private provider. My secondary e-mail is hosted by a different small private provider. Then come Apple, Google (mostly for groups) and Microsoft.
You call that a temper tantrum? I thought he was being very reasonable.
No, it's row-level partitioning — splits a single logical table into multiple physical tables.
A lot of microcode is about things like segmentation and TSS.
Hasn't the CSR BLE mesh been around for far longer?
Thanks for the work you & the team have put into Jest. While I haven't used it recently, I'm glad that it's out there as an option. The _ability_ to mock easily was always super great.
I agree with most of what you say, and agree this is an uneconomical idea. However, I think the more likely scenarios at the end of the process are that the plastic either ends up in a landfill after use or ends up being recycled. Both of these outcomes will not release all the CO2 back into the atmosphere since common plastics do not break down when buried in landfills.
In the case of LA and San Francisco, they're really good places to put ports.
Underrated post :) This was the first thing I checked too. I run GNU/Linux. My internal web cam has never worked.
What's the most interesting story you've had to censor because of this experiment?
How much danger is there really? The risk of being injured during an earthquake in the modern era is pretty low, all things considered.
Google Makes So Much Money, It Never Had to Worry About Financial Discipline
Used-car marketplace Beepi shuts down, merges with stealth Fair.com
Node has concurrency?
:P
Hello!

IO is an experiment. It's a free, lightweight editor for creative and authentic publishing. ️

It's extremely easy to use and allows you to publish anonymously, under a pseudonym, or as yourself. Our vision is to make writing and sharing your thoughts easier than ever. The editor is a little rough around the edges, so be gentle (many improvements are on the way!). We plan to build on this idea in the coming weeks and months.

This is your blank canvas.

This project (started only a couple weeks ago!) is brought to you by a very small team. We have much more to come in the near future! Meanwhile, please email me at d@bold.io if you have any questions/suggestions or just want to talk product. :-)

Meanwhile, kick the tires at https://bold.io today, bookmark it for later and publish freely any time.

More info: https://bold.io/about-io-2016-12-06

P.S., this link is fun: https://bold.io/random
Most definitely, it would be difficult to come up with metrics for developers that both rewarded the right behavior and were not game-able. The "ideal" I proposed is probably unachievable.

For instance, I once had "customers repeat app usage" as a KPI. This aligned with the company's goals for this mobile app, but resulted in pressure to add "dark patterns" and product features that annoyed people into launching the app. If the metrics are simple and naive, you're going to get employee behavior that has unintended consequences.

That said, I'd still argue that any steps taken to make one's performance goals more transparent and _measurable_ are steps taken in the right direction. If I knew what those magical "right" metrics were, I'd go into business tomorrow an HR consultant.
From a toxicity point of view, I believe that is the part of politics that should be avoided here. Specifically all the sludge that revolves around candidates competing with each other, instead of focusing on the issues themselves. In fact, if politics consisted of only discussing the pros and cons of various policies, laws, and positions, then it may actually be informative.
Because their obviously not acute? :P
Is there any concrete possibility of colonising another planet? Here in the comments for similar stories I see lots of scifi talk about the topic but little concrete arguments other than some amateur maths and physics. I know me some astronomy and even colonised Mars seems pipe dreams to me. Am I wrong?
Hurricanes and snowstorms are predicted days, if not weeks in advance. The scary thing about earthquakes is that they can hit any time with very little warning.
All of your arguments would apply to any other big tech company like Google/FB/MS. Then why don't we hear as many negative stories about them?
Antibiotics are extremely expensive to develop (on the order of billions of dollars), and patients regularly die because 1) the antibiotics were ineffective against the particular bacteria in their body or 2) the antibiotics wiped out their normal flora, and give them intractable cases of C. difficile and the like.

> zero other options

Those patients literally had zero other options than just dying.

Phages should be another weapon in our arsenal. You're right that they might not end up working out, but right now there is chronic underinvestment in research to find out whether work, because nobody is going to heavily fund research for therapies that will never pass the regulatory hurdle. It seems like bad risk management to back ourselves into a corner -- the whole point of research is to find out whether other things work. Defense in depth isn't just for software security.
Yea, there aren't many places on this earth that don't see some sort of natural disaster. Maybe we'll all be living in the UK/Ireland, they don't seem to get hit by much.
the purpose of self assessment is so that your manager doesn't need to provide useful feedback, or take any sort of stand whatsoever. You sell yourself and as long as things are ok they stamp it "OK sounds good"
Smith, Winston! Recite quicksort into the telescreen!
A xeon would be a poor choice for a gaming rig. More money for lower clock speed.

Edit: you guys can't seriously believe that a xeon is a good gaming CPU...
The big one will happen, and it's going to suck, but it won't be the end of the world. Modern structures built to more exacting standards will still be standing. Infrastructure like water and electricity will be unusable for some time, but with immediate stores of water and the inevitable aid this shouldn't be deadly. I'd be nervous about spending a lot of time in old, brick buildings, but otherwise I expect that I and most people I know will be fine. Note that this is said as a resident of Seattle - I would be way more nervous if I were on the Oregon coast.
> documentation for each language's standard library is pre-installed

I've never entered a programming competition but I'm glad to hear there is still some sanity left in this world.
A Conversation with Brian Roemmele on the Voice-First Future
Thoughts on clojure.spec
The NYT article even mentions Signal weaknesses (e.g. multi-device support) that are addressed in Wire, without mentioning Wire. Poor journalism.
But then keep that line of thought going. Mars has the pieces it needs to form dna like molecules, at least in some protected environments, like in the salty almost frozen water slightly under the surface, so there's a very likely possibility of life being related to or similar in process to our life on earth.
but unlike earthquake, you have ample time to at least save yourself, no?
Earthquake insurance is pretty darn expensive, and most (all?) homeowner policies don't cover earthquake damage. Source: I used to be a licensed property and casualty agent in California.
You can't argue that it's a weird idea to ban something you can't even define, even as a one week experiment.
Was a particular diameter part of the patent? Or was it just rounded corners?
How to set up DIY video monitoring for home or office – subscription free
The Big One in California is expected to have Richter magnitude below 8.0, much like the 1906 one. While that might not be much consolation, building has improved significantly and we can do a lot to prevent damage. That said, after having been in the market for a house on the east bay, I'm afraid to say that there's still a huge number of old houses with brick foundations, despite incentives to reinforce and retrofit. My biggest fear is not the shake itself, but damage to power and gas lines shortly after.
Eat healthy, exercise, don't smoke, stay a good weight.. you will do better than average, on average. I think this is all just a trend of our not healthy culture. If over 10 years everyone gains 10 pounds, your life expectancy is not going to do awesome things.
Code with style with Atom power mode
Second monitor?
What’s the best way to sell products online?
> In 1299, zero was banned in Florence, along with all Arabic numerals, because they were said to encourage fraud. Zero could easily be doctored to become nine, and why not add a few zeros on the end of a receipt to inflate the price?

I'm really curious about this part. It sounds like they were already using Arabic numerals. How did they intend to express numbers like the ones mentioned in the first paragraph, like 101?
People get too hung up on the question "to test or not to test" instead of asking the question "where and when should I test".

I started my career writing iOS clients, and the obsession with TDD was baffling. 80% of my code was usually either UI or simple Core Data manipulations, while the last 20% was mostly API parsing and a touch of business logic. I wrote a few tests for parsing corner cases or business logic, but they never really gave me any confidence or helped with refactoring, instead taking up time and adding overhead whenever I made changes. I supposed I didn't have enough coverage to get the benefits, but what tests would I write for my UI? What tests would I write for simple Core Data queries (which is assuredly unit tested already)? What tests would I write for my parsing libraries (which are already unit tested)?

Then I started working on the (Python + Flask) API backend, and tests were self-evidently necessary. Python is dynamically typed, which can result in lots of corner cases when doing simple data manipulations. Python is interpreted, which means the compiler/IDE won't warn you about syntax issues without running the code, and you can't catch even the simplest logic errors without running the function. Most importantly, the API's entire job is translating data, inputs are in the API parameters or database, and output is the JSON. It's a perfect function, and tests were obvious. I wrote something like 600 in a week, then used them to make some major refactors with confidence.

What I learned from those juxtapositions was that unit tests and automation are invaluable in certain circumstances. Specifically _any system that creates machine-readable output_ like JSON, populating a database, or even a non-trivial object factory should be unit tested like crazy. Any system that creates human-readable output, like views or changes in an unreachable database (something like an external API or a bank account) needs to be human-tested, there's just no way around it.
There are specific laws to protect rights beyond the realms of "speed".

Apply your line of thought to democracy and you'll see what's the problem.
...Because if the coworker had to explain it the first time, you probably aren't qualified. Depending on the job, of course.
Good point - I'd bet it applies to autism and such too.
I used expect heavily at several clients in the past and have never seen someone else use it. I never used it as a precise tool, rather as a Sledgehammer. I think I remember I used Expect to script remote machines (expect was literally the "programmer") when everything else failed and was "prevented" due to policy. I guess my script was also non-compliant, but noone complained.
Useful concept: https://en.wikipedia.org/wiki/The_purpose_of_a_system_is_wha...
Next year, Facebook becomes a teenager. Just how long does the founder get founder privileges?
I wonder what would have happened if he had initially told the CEO it would take 6 days for the change?

"We can do that, but it will take us 6 days, otherwise we risk taking the plant down and aggravating the issue."

I wonder if the CEO would have just said ok thanks.

In my experience that's the case. The engineer in that link got himself in a bad spot, because he didn't know what was involved for the change when he communicated his estimate. And most of his back and forth that slowed him down would have been avoided had he known beforehand how to properly do it. Even with everyone's feedback it sounds like a 1 day code change. That seems to me like the reason the change was slow is more ramp up time for him working on a code base he doesn't normally work on.
Sure, but that's not trivial. E.g. in many cases these are people who might be unable/unwilling to work any kind of regular or fixed hours, so making this a regular-employment job would hurt those people.
I'm curious and didn't see an answer to this question while reading that link (or the link to the original source) -- how does 'median tenure' distinguish between a company where people are leaving quickly, and a company that is aggressively hiring/growing? A bunch of brand new employees drags down median tenure without necessarily being a sign of massive turnover.
I write code that interfaces with hardware (health care imaging systems), processes images, and a little computer vision here and there. Very few service calls in that stack.

I jump up 1000 levels of abstraction from time to time, and when I do, I agree that security is extremely important (FDA class III device and HIPAA compliance is mandatory.) I'm also a lead, so I have to know enough to call BS when I hear it from a team member.
Well, now I've downloaded and installed Wire alongside Signal on my phone.
> i got an offer from them without ever interviewing in person.

May I ask what the process was (steps) and what kind of accolades you have?
I just stayed in NOLA last week in an Airbnb and the building (high end condo building) had posters all over it saying "We do not tolerate short term rentals as of xx/xx/xxxx)
I'm a vim-guy. I've been using vimoutliner (https://github.com/vimoutliner/vimoutliner) for my todo lists, since I put my notes inside my todo lists. With vimoutliner, you can make any line have a checkbox [_], and it understands that a top-level is done only if all of its children are done.
Frequency or intensity: choose one. I spent plenty of time in the basement of the house I grew up in waiting for something to blow over. I've experienced one earthquake in the same amount of time in WA, and it didn't really do much whereas a tornado was responsible for the entire roof structure we had to replace on the barn (thankfully we had left said barn for the house just moments before).

Anyway, the point is that, no, we should abandon the entire west coast only to end up reliving the opening scenes of The Wizard of Oz. The universe has a lot of sharp edges, and they're everywhere.
No worries. I'm looking forward to trying it out again after things quiet down a bit.

Fyi, it doesn't have to be a $500/mo server permanently either. Depending on where your hosting the backend, you could scale it up temporarily and then scale it back down when things quiet down. $500/mo is approx $16/day which could be well worth it for a day while enjoying an HN-driven bump.
There is no cost-effective way to get residential earthquake insurance in the Bay Area.
Yes, it does. On the other hand, though, you can get a cheap Windows laptop for less than some college text books.
I have used Jasmine+Karma. It's good stuff. It doesn't have the the "awesome stuff baked in" feel that Jest gives but it also doesn't give you a headache when something baked in doesn't work as expected :).
> Which leads to the 'callback hell' that we all know and hate. Part of the bill-of-goods we accept when using Node is that in exchange better time and space characteristics, we lose the thread as an abstraction.

Perhaps my head has been stuck in javascript/node land for too long but I think accusations about javascript producing callback hell now seem a bit disingenuous even for relative novices to the language.

It's 2016 and there are many well documented and widely adopted solutions arising from external libraries and developments in ECMAScript. Thanks to transpilers like Babel/Typescript we can even shoehorn these new ECMAScript features into older browsers.
There's a difference between earthquake and tornado/superstorm/flooding/etc. in that earthquake will strike you out of the blue with literally NO warnings before, but those other disasters at least give you a time-window to prepare.

Some people just don't like getting surprised!
Google data centres to be 100% renewable-powered by 2017
Every image is searchable with Inception and a Crawler in Google Cloud for 0$
That improvements in healthcare can't keep up with the bad choices we make when it comes to nutrition and exercise.
For some, there might be some valuables on these interviews:

https://www.youtube.com/watch?v=QVpSIdWE0do&list=PLEMXAbCVnm...

Again, it's game dev oriented, but there are good general advice as well, here and there.

Mike Acton is on there too. Jonathan Blow, Ron Gilbert, etc.

In general, I think more programmers should be concerned with learning how things work at a deeper level than the API for whatever web framework they are using. Web applications are god-awfully slow, it's like the programmers behind them just don't give a shit about performance, at all. It's not that much better on the desktop side either.
Amazon is doing many great things, however the way they are going about it is starting to freak me out a little bit. This is how we end up in the corporate dysutopias described in Neuromancer and Snowcrash...
Don't we somehow have to take a step back and try to avoid this, rather than keep trying to optimise our hiring processes ?
I finally wrote my own editor so that I'd have something that works exactly the way that I want an editor to work. I don't need a built-in e-mail reader or ELIZA clone or scripting language, just really good interaction with UNIX text processing commands.