skysight-inc/HackerNews huggingface dataset:
Pantheon, located in San Francisco, is looking for an Senior Web Developer

Pantheon powers the world's professional websites. Our multi-tenant, container-based cloud platform enables businesses to run mission-critical Drupal & WordPress websites. Developers, Marketers and IT can instantly scale in response to unplanned traffic spikes, without upgrading VMs or clusters. Large enterprises use Pantheon, including Intel, Cisco, Arizona State University, and the United Nations.

We're looking for a Senior Web Developer to build amazing Web and interactive experiences that delight visitors. You'll have the support of a world-class team of Web experts (that's our business) and a healthy budget to work with agencies and contractors to create a unique presence for Pantheon across multiple websites, marketing campaigns, and third party sites. You won't have to worry about servers, software, networking, databases or caching... Our platform takes care of all of that infrastructure!

What's in it for you? * Industry competitive salary.
* Stock options.
* Vacation days and time off.
* Full medical coverage (medical, dental, vision).
* Top-of-line equipment.
* Fun at Drupal community events.
* Discounts on custom bicycles - the founders of Pantheon also founded Mission Bicycle.
* Dog friendly office.
* Training stipend to attend industry conferences.
* Fully stocked kitchen with lunches provided.

For more information, visit: http://www.thesourcery.com/jobs/861
NASA Eyes Mission to Jupiter's Ice Ocean Moon
Dynamic languages was a breath of fresh air compared to the clunky explicit typing of Java. The first versions of Java didn't even have generic, so just using collections required lots of explicit casting to make the compiler happy for little benefit.

But today the breath of fresh air is powerful type systems and type inference which provides the benefit of typing without the syntactic overhead.
Because there is an entire industry of which Intuit is part of that profits off the complexity of current tax system. Simplify the system and profits go down.

HR Block was caught lobbying against simplification of the tax system for this very reason.
Disclaimer: I work at http://www.pagerduty.com so feel free to tar and feather accordingly.

Carrying the duty pager is a painful experience for some fraction of companies, BUT the long term trends are promising. Here's what I'd keep an eye out for (I've been on call for ~5 years):

* Does being on call affect your other commitments? At PD we scale back the number of predicted story points by ~50 for the devs that are on call.

* Are you empowered to permanently fix the root cause of whatever woke you up? (that's where that 50% of time goes) If you aren't, that's a big red flag. Not all developers take advantage of it, but the ones that do are much happier once they kill the root cause with fire.

* Are you compensated for on call? Among our customers, we have a few that pay $500/week for on call duty, that seems to be the rate at which you can easily find people to swap shifts with.

* Make sure you are off call sometimes. Seriously.

* Who owns the pain report? Someone needs to track how often (and when) people are disturbed and make sure that you are making progress as a team (Github's Ops team is amazingly good at this). If the house is always on fire, you're not a firefighter, you're a person who lives in a flaming house.

* Is it a NOC model, where you can write down common things to try to solve a type of problem (and then you're only paged as an exception) or are you paged for everything? (That's a severe over simplification)

* What is the expected response time? What is the required response time?

* How are you onboarded? The worst time ever to fix a problem is alone, with no context, while things are broken at 2am.

That's off the top of my head; there's good advice in this thread. if you're still lost though, feel free to reach out to me: dave@pagerduty.com
New York City’s Tech Boom Continues
honest question: why is the lack of diversity in tech a problem from your point of view ? I don't know any other field where people perceive these kind of problems. (I never heard anyone wanting more women in construction or plumbing nor more men in nursing for exemple)
It looks pretty neat, good luck!
It isn't quite that simple. Real estate is one of the most widely-available assets that can be as levered as it is allowed in so many nations.

This leads to perverse incentives. A property owner with a paid-up property can lever up, kick out tenants, post an out-sized rental rate, and use the credit to cover costs and missing income until a new tenant willing to pay the rental rate steps forward. Usually they step forward with the simple progression of time and inflation catching up to the new rental rate, or it's a business more heavily capitalized and banking on serving much more flush clientele (interesting discussions around the bifurcation of the economy and just how many businesses can thrive crowding into that wealthier end).

This puts lots of incentive to keep inflating real estate valuations until the credit spigot is turned off. Meanwhile, the hands on the credit spigot gets paid by the velocity of credit granted, so they get lots of incentive to keep granting credit on inflated valuations. This circle turns until it doesn't, usually with some form of falling demand exposing who wasn't wearing swimsuits as the tide goes out.

Contrast this with the asymmetric credit access available to most small businesses. They could have a longer tenure and track record than the present owners of the real estate, but still be considered a great risk because (rightfully) the credit granter will assess growth prospects to practically nil. So faced with a 200+ year old business that can definitely pay back $100K in five years, or a new property owner of the underlying real estate that might, maybe, possibly pay back $2M in 10 years if the right valuations can be signed off, which deal looks better come bonus time?

This isn't a nefarious plot or the yield of some evil; it is simple human nature played out on the canvas of time and incentive structures. There are some interesting issues to ponder here with how agency, compensation and influence are structured in the valuations process, and how that ties in with the overall cycle. As well as many other factors that don't show up on an initial cursory take of the industry. But suffice to say...it isn't quite that simple.

As for what can one individual do about it, that's a fascinating and long discussion in itself.
Several have asked about node.js in contrast to io.js. It's fair to say that the emphasis of node.js at this point is on stability (including API stability, production debuggability/observability, etc.) and performance -- in that order. It definitely takes longer to release software when operating under these constraints; as the team writes in the linked blog entry:

We are also pleased to report that this release of Node.js has tests passing on all of our supported platforms. On the one hand, this seems obvious (what are tests for if not to verify before you release it?!), but this is actually the first release of Node.js that has operated under this constraint. Requiring that all tests pass before releasing Node.js marks an important development for the project, and is essential for building a solid path moving forward.

It's unclear what the divergence will be in the future, but the emphasis of the node.js team on stability may or may not be shared by io.js -- and in particular, this may be reflected in things like the V8 version, changes in which tend to subtly break esoteric things on different platforms. Inasmuch as the divergence represents different operating principles (i.e., enterprise-grade stability vs. bleeding edge), it may well be helpful -- and I think it's entirely conceivable that the projects will develop a symbiotic relationship moving forward.
A mandatory national identity card would be an ideological non-starter to the small government wings of both parties, despite the fact that the information industrial complex would love a government project of that scale to attach pork to.
I've had the opposite experience. I've only had a couple modules that use native code that haven't worked, and most of those monkeyed directly with V8 so I wasn't terribly surprised they didn't work with the upgraded version.
Overall a bad article, but the issues it brings up are important:

> The financial strain Koch has endured underscores a cruel irony that has only recently come to light.

No, that's like saying that women being treated lesser than men "has only recently come to light". Open source, even (especially!) the core, important stuff is blasphemously underfunded, and it always has been. Everyone knows this, even those who deny it.

Furthermore, the psychology is uncomfortably close to the psychology of misogyny: historical precedent, deeply rooted social structures (in this case driven by software economics), by and large nobody wants to pay the significant costs of fixing it, and every now and then a truckload of goodwill is dumped on the fire to douse it so we can all forget about the broken system we're working with until the next time it breaks.
I stopped doing this once 64 bits became a thing. There's nothing wrong per se with having your indexes signed, if you don't mind potentially not being able to access the entire array - though I'm not convinced using int is very forward-thinking, as they're fairly reliably still 32 bits - but there's everything wrong with casting size_t to int.

For example, assuming 64 bit, suppose i is 0x1000 and container.size() is 0x100000fff. Now (int)container.size() is very likely to be 0xfff, meaning i is greater, and something goes wrong.

Or - and this would be very likely true for 32 bit systems as well - suppose container.size() is 0x80000000. Now (int)container.size() is -2147483648, meaning i is greater, and something goes wrong again.

A better option would be (assuming size_t is at least as wide as int, which is vanishingly unlikely not to be true on modern systems, and can anyway be checked for using a static assert) i>=0&&(size_t)i<container.size(). Then you know the cast won't produce nonsense.
Rust isn't ready yet so I wouldn't pick that.

Scala I'm not familiar with.

C++ is great. Very fast and powerful, and really not as complicated or difficult as people make out. The manual memory management thing isn't really an issue if you do it right. However writing multithreaded C++ code is never fun.

Go is very simple and easy. I think of it like Simple English. It's very easy to write, and everyone will understand what you are saying, but you'll end up being way more verbose and often a bit more clunky than you might be in a more powerful language like C++. Huge limitations are that there is no overloading at all. I.e. you have to implement `minFloat64(a, b float64)`, `minFloat32(a, b float32)`, `minInt(a, b int)` and so on, whereas in C++ function overloading means it is just `min()`, and templates mean you only need to write it ones. The other big issue is lack of templates (AKA generics), so containers (list, map, etc.) are a pain in the arse to use.

However Go does have great concurrency support, and is close enough in speed to C++ that I'd probably always choose it to write servers in.

So I'd say Go, maybe C++. In a year reconsider Rust.
Here you go:

http://watchdog.org/96500/illinois-rewarded-for-misspending-...
Announcing Free Paper Tools
Because $$$. A financial handicap is the worst kind of social handicap.
This is one of my disappointments with Jolla/Sailfish - they give the impression that they don't care one bit about allowing end-users be/become developers/hackers of the system (or help port it etc). No easy to access public repo, no build instructions...

It appears FirefoxOS is our last best hope (for open devices running open code). Unfortunately I'd be more interested in a system like the original Ubuntu vision than what I understand FOS to be (not that it's a problem that Moz makes the product they want - it's just not the product I want). Maybe the kernel/init/rootfs of FOS can provide a solid foundation for a fork, along with a supply of actual hw to run the thing on. Unlike ASOP/replicant which only works on a small subset of devices despite the GPL protection of the kernel.
Because Congress never votes for a reform of tax codes because the lobbying from Intuit and HR Block et al is too strong, while there's no lobby for the populace at large to say "This sucks."
I'd also add here that you can add other variables in to the mix such as gaussian noise and drop out which is the basis for a lot of fundamental neural networks. I get the intent, but it's not necessarily the case.

Neural word embeddings are one of the most fun things I work with. Both word2vec as well as glove and paragraph vectors.

There's also the ability to learn varying length windows of phrases via recursive or convolutional methods.
"I find that a much more comforting idea" is not the most compelling argument I've ever heard.
Not just that, but useable, well thought out configuration, a few custom packages, whatever kernel is required to make a bunch more hardware work OOTB and some taste applied, something that's sorely lacking in many linux distros.
They are working on web-like APIs so you don't have to necessarily deal with the native platform for basic stuff like file/network access, etc. For more advanced stuff it's super simple to make your own wrapper. But yes, this is a constant downside to anything like this (only thing to compare is how difficult it is to wrap, and they aren't done with that part yet).

For #2, there's actually a great story. You can literally run the JavaScript inside an existing engine, like Chrome or Firefox, and serve it from there. You can use the normal devtools and set breakpoints on the JS.
Free Mentoring for Beginners Learning to Code
Example? I'm curious because mostly everything has worked for me.

I'm using:

io.js v1.1.0

npm v2.4.1

node-gyp v1.0.2
Congratulations on the emptiest website ever...
Nitpick: they wanted your money. It's not "theirs" by any stretch.
Seems more like a badly constructed phrase than an incorrect fact: http://www.truesparrow.com/
Not sure if this is a joke, but assuming it's not - it's the standard now, and it's been out for... 2 whole months?!
It seems like every 2 or 3 months there is data-breach in the news and a bunch of plain-text info is stolen. And ever-time I am inclined to imagine the companies storing in plain-text would think "oh we should change something about this"

But then it happens again 2 or 3 months later anyways ...
It's also easier to say when you have a lot of money. Telling someone living in poverty that money is fictitious would be pretty tactless.
Full disclosure - this is my employer and a product I work on.

For enterprises, and folks outside the enterprise communicating with them, commercial products exist which effectively allow any sender to use any email address as-if it were a public key, even if the recipient hasn't set up any sort of encryption yet.

While compatible with PGP, this is not PGP encryption, but I figured this may be of interest to readers in this thread.

White papers can be found at the bottom of this product info page:

http://www.voltage.com/products/securemail/
Indeed; what I'd really hope for, in the end, would be just beginning to teach discrete math (logic, set theory, graph theory, etc.) to kids starting when they're 11 or so. It's a lot easier, and a lot more fun, and tends to be a lot more appreciated by the kids than the random bits of pre-calculus (literally "things that are useless unless you later take calculus") we teach them in "Math" class!

But, of course, everyone always derides the idea because "we tried this" with New Math in the 70s. No, we didn't. We tried to teach some parts of discrete math (which are formal abstractions) to 5- or 6-year-olds, who weren't yet at the formal operational stage of cognitive development. You can't teach a 6-year-old about set theory any more than you can teach a 6-week-old about object permanence. You have to start when they're older. But "older" doesn't mean "an optional thing to be taught at university!" It's a formative skill, and if you don't pick it up right when you're first able to pick it up, trying to force it into your mind later is somewhat like trying to learn a new spoken language in adulthood when you've been monolingual for your entire life until then.
It seems to me like the bulk of "security research" these days is vulnerability discovery. This is certainly important. However, more profound solutions like capability-based operating systems (e.g. CoyotOS), and in general forward-thinking projects that aim to provide comprehensive foundations for secure systems seem to be left behind and neglected in favor of continuing the present rat race of applying band-aids and bug hunting our existing cruft.

Unfortunately, a "Manhattan Project" for cybersecurity wouldn't really work because the problem is a highly multi-tiered one without a clear end goal, with a lot of individual bits and pieces that are visible and have potential to be refined or started anew.
Articles like this must be why Putin wants to build his own "regional electronic encyclopedia."
Thankyou sir :D
I dunno; they have deep pockets, and state AGs can be pretty aggressive if you make it worth their while. I could easily see some state AG taking them to court on a variety of theories if they are actually the source.
React + Reflux + Webpack workflow framework
Creating a workflow framework to make life easy for developers to develop React and Reflux application. It used webpack and gulp to make development and build process workflow a piece of cake for developer. Almost zero setup ~

React + Reflux + CoffeeScript + Stylus with Gulp + Webpack

Check it out and feel free to fork it :-
https://github.com/iroy2000/react-reflux-boilerplate-with-webpack
So, assuming the medical industry in the developed world gets out of the way (which I don't think is a foregone conclusion...it will take years, and possibly too many resources, to bring this to market in the US for a variety of good and bad reasons related to our regulatory environment), this is potentially one of the biggest revolutionary changes in healthcare in my lifetime.

This makes detection of both viral and bacterial infections possible with very low-cost tools; the fact that it can detect both makes me believe that detecting practically any infectious disease (or at least any infectious disease that has identified biomarkers in blood, or other easily obtainable bodily fluid) is on the near horizon.

One could buy this dongle, or one like it, and new diseases could be added via software upgrades (or by in-app purchases for the diseases you want to check for). This would potentially make doctors office visits obsolete for all but serious disease and chronic conditions. No need to go get checked for strep when you have a sore throat (of course, getting the antibiotics to treat it is another regulatory hurdle people in the US would face), lower need for cities and universities to provide STD testing, though treatment and education would still likely be within their perview. It allows better self-management of HIV, hepatitis, Lyme disease, and other chronic viral illnesses through more rapid and frequent testing.

Even if this doesn't evolve to include other types of detection, I would still happily pay several hundred dollars for a re-usable STD testing tool. I like to get tested every 6 months, but the hassle and cost of going to the doctor or Planned Parenthood or online testing lab is high (free or low cost testing is available, but you trade much more hassle for the lower cost...among my friends who get tested at the city health center, they usually spend an hour or two waiting, which is not a cost I'm willing to pay to save a couple hundred bucks). If I could test for HIV for free before every new partner (and, hell, make it a practice to test with every partner), that'd be fantastic.

Another article about this was posted a week or so ago to HN, but it didn't get any comments or many upvotes, which was disappointing, as this seems like entirely revolutionary technology, to me. And, it makes me want to go into medical tech because of how huge the potential is (but it would be an entirely new field for me, so my ability to be productive in it would take a while to develop).
yeaaaahh, speak to me when you have a RC
io.js is built against a much more current version of V8, which notably has default-on support for a lot of ES6 stuff.

Quite frankly, as a casual node user myself, I'm sticking with node v0.10 for the time being. I want to see how everything shakes out, and my site runs okay for now.
Greg Egan has a whole lot to say about 4+0 spacetime: http://gregegan.customer.netspace.net.au/ORTHOGONAL/ORTHOGON...
That's fascinating; I would have expected the reverse: that people who are biologically male but identify as female would have had low developmental androgen exposure, thus a more "female-structured" mind that leads them in this direction, and thus have average aptitude for mathematics closer to that of neurotypical women.

What you're saying instead suggests that it's actually the continued androgenizing effect of male gonads on the body during puberty that determines whether the brain dimorphisms responsible for different mathematical aptitudes develop. Neat!
Show HN: I built a a web app to visualize density functions
Why don't you push nodejs forward and track the latest v8 (or whatever the latest stable chrome is using), and then cut LTS releases at regular intervals, kindof like the kernel or ubuntu?

Also, are these tests public? How many does iojs pass/fail?
Seems like a recipe for disaster. Have there been any companies that actually accelerated this fast and made it work?

> The board [...] approved a plan to increase Fab's burn rate to generate $200 million by the end of the year. The plan would drain Fab of its remaining capital by August, but as long as Goldberg was able to raise $300 million more by then, the company would be fine.
I'm really excited that this version of Node includes updates I made for the debugger module[0], including the ability to show you the closures in your program[1]. (This has already helped nail some memory issues in Node itself.) I hope to blog about it in more detail next week.

[0] https://www.joyent.com/developers/node/debug/mdb

[1] https://github.com/joyent/node/issues/8718
> One solution is to collect a payment when you buy a new gadget, then you get it back when you return it for recycling.

that's an excellent idea.
iojs is definitely not the "standard" by any means... It's accelerating at a quick pace, but I haven't heard of any major sites making the switch yet. Many native modules (node-gyp compiled) aren't functioning yet, and the streams module was a bit finicky as of a couple weeks back. I'm looking forward to the market competition actually. Can't go wrong with having two standards battle to be the best.
my healthcare provider (Anthem) was just hacked, so my SS number and other identifying details are probably being traded on some Russian web site right now.

Anthem did not encrypt the data which was stolen.

Sony did not show any signs of basic competence in its data security either.

a Manhattan Project is useful if you have a really tight deadline, a very specific and achievable goal, and the problem you face is one where the technology you want does not exist yet.

but everybody in technology knows that the technology exists, and the problem is widespread incompetence and indifference.

the solution for that is not a Manhattan Project. it is class-action lawsuits.

think how fucked up this situation is. everybody in infosec knows that Anthem and Sony were ridiculous and 100% at fault in their negligence. yet people who get their info on this from the mainstream media have probably never even heard that point of view.

so you get utterly uninformed commentators who think that Anthem and Sony must employ geniuses of the first caliber, and that we need to take the "new" and "unprecedented" step of classified crypto research.