skysight-inc/HackerNews huggingface dataset:
Great comments - but one bit of feedback on the iPad as dissapointing - https://9to5mac.files.wordpress.com/2015/04/cumulative-shipm... shows that 57 months in (the age of the iPad so far), the iPad has sold more units than the iPhone at the same time. The issue is, growth has actually started dropping.

So - the iPad started out stronger, but then stalled, whereas the iPhone started out "slow", but then started accelerating.

I have to believe that the iPhone 6+ put the breaks on a lot of people's purchase of the iPad. I never used my iPad while I had the 6+, but then, when I left (sob) my 6+ in a cab, I found myself using my iPad again more frequently.
"I don't think this paper is very useful."

That's probably correct. The author discusses a known problem; those mis-labeled images are well known, and have been discussed on HN before. It's clear that feature extraction in deep learning sometimes fastens on irrelevant features that somehow work. Some algorithms result in models where data points are too close to at least one decision boundary in a high-dimensional space, which makes them brittle when faced with small, noise-type changes. I don't know enough about the subject to know how that will be fixed, but there are people working the problem and they don't seem to be stuck.

Then the author, who is from OpenCog, goes on to claim, without supporting evidence, that OpenCog can somehow fix the problem. The paper proposed an "internal image grammar", but doesn't say much about what they mean by that or how to do it. Trying to decompose images into some symbolic representation has a long, disappointing history. The computational neural network people are getting results without doing that.

I think we're reading a grant proposal here.
I suspect enums have uses, as do the improved async code constructs (and there's more of that in the pipeline).
Its extremely subjective though. For the first few years after starting, I thought that large functions were bad and should be split up unless theres a clear reason not to.

Now, I feel that it should be the other way. Most of the time you want to keep the code that does something together, splitting it up only to factor out common reusable pieces (that are actually reused).

This is also discussed in the linked article.
I understand that but I can see fellow founders condemn other founders for taking an above avg salary or as was the case with the founders who took $6m [0] off the table during funding...

Surely the Lp's should look at such high salaries as exorbitant..

[0] - Secret App that has since closed shop
That would be very inefficient, because registers cannot be indexed. The dispatch you have to introduce to jump to code that references the right physical regs would murder you with mispredictions.

Also, register VMs typically have three operands. Specialising each instruction for each possible register for three operands would result in a ridiculous volume of code.

Special purpose instructions that access fixed registers would be fine, but general purpose operand references cannot be sanely implemented in this way. Existing register VMs use memory because it's faster.
> It is a 3-axis CNC machine combined with an electroplating head.

Erm... CNC Machines can cost thousands of dollars. I think this guy made a $2 attachment to a CNC Machine that then spits out copper.

Which is cool and all, but the headline doesn't seem right to me.
Human Eyes Are Wired Backwards
For what it's worth, that's a fair concern. I offer two things that make it not quite as bad as you may think, though :-)

1. We don't expect applicants to be amazing at this already. Having a background in security is good, of course, but not necessary. As a data point: in the office I work out of, we have someone who used to work in a bakery, someone who worked for an insurance company, and several people who had never done security before applying to Matasano. It's my opinion that you generally learn more "on the job", as it were, than you would preparing for an interview anyway. @tptacek's post at [0] is a good example of the type of people we have working for us.

2. We generally send candidates resources to help them prepare - I believe a couple recent applicants got free copies of "The Web Application Hacker's Handbook" [1].

[0]: https://news.ycombinator.com/item?id=8395627

[1]: http://www.amazon.com/The-Web-Application-Hackers-Handbook/d...
Good to hear -- I've been interested in the Activité, but haven't gotten my hands on one to try it out yet. I like my Fitbit for keeping me honest about walking around and whatnot, and my analog watch doesn't do that for me, so I find myself somewhat ridiculously wearing one on each wrist.

In your experience, what are the downsides of the Activité, vs. a regular old analog watch?
http://typedrummer.com/e2t041
Well they can charge all the expense to the fund and still take nominal salaries.

The startup world isn't encouraging of founders who take high salaries or who take money off the table..

Some of this exorbitant salaries could have been paid to extend the runaway of key startups and generate better returns.
Good job. What proof, may I ask? What was the mistake, and what tool did you use? Is there a paper on this I can read?
In addition to the 8020 beams already mentioned, there are also MakerBeam (http://www.makerbeam.eu/) and OpenBeam (http://www.openbeamusa.com/).

Primarily they are used for building structures quickly and easily - a saw and a wrench are the only tools you need. The standardized brackets for each beam type allow you to make 90 and 45 degree angles.

But they are often used for more than just framing. The 3D printing community has embraced extrusions because you can also use them as bearing surfaces, mount motors and servos, limit switches, etc. Basically anything that has a hole big enough for a machine screw can be mounted to a beam either directly or through an easily made mount (usually to get the angle that you want - all it takes is some sheet metal).

The quickest way to learn is to look at examples. The OpenBeam website has lots of examples. The system is so simple that you can understand exactly what is going on just by seeing a picture.
Collectively, the three of us have interviewed dozens of times over the last 3 years. The description is based on this, so it is not just hearsay.
Don't believe Orson Welles
Apparently the whole 6502 has only 3510 transistors!

https://news.ycombinator.com/item?id=2064030

To compare, modern Intel i7 processors have around 2 billion (some less, some more).
well if you take "sparse autoencoders"(http://web.stanford.edu/class/cs294a/sparseAutoencoder.pdf) they basically give you principal components of the data, so from blobs of raw pixels you get a "dictionary" of lines in different orientation and size, like an edge detector. This is also similar to how the famous Fourier transform works ( http://en.wikipedia.org/wiki/Fourier_transform), it decomposes the raw signal like speech into its base forms or "harmonics". And if you add another layer (to a stacked autoencoder) it will extract higher level forms(e.g. basic shapes like triangles, ellipses etc) and so on until you get a dictionary of different forms, with each layer kind of compressing the signal into more compact summary. At the higher layer you can arrive at the abstract "chair" or "cat" representation which is based on all these lower level forms: shapes, lines and dots.

Then once you got this dictionary of image "words", next thing is to infer how these words interact with each other, i.e. build a grammar (it's also called "grammar induction" in natural language processing http://techtalks.tv/talks/deep-learning-of-recursive-structu...).

By learning a grammar you essentially define a concept of "chair" or "cat" at a higher level of abstraction by determining how these forms relate to their world (i.e. to other forms), e.g. you can determine that "cat sits on a chair" is a legal phrase in the grammar and "chair sits on a cat" is not.

So extracting a grammar (visual or linguistic) from training data is equivalent to restricting the system to common sense reasoning which operates on concepts in terms of "production rules" of the grammar: http://en.wikipedia.org/wiki/Production_(computer_science), and it is a basic goal of AI.
That pretty much sums it up for me. I wouldn't have done it this way, but we are too far ahead on the Python 3 line and it's probably time to let go off the debate and move on to Python 3, at least for new projects.

Needless to say that the Python web developers community was set back by couple of years due to diverted attention. When Python should have been looking at concurrency and async support, everyone had to get busy maintaining duplicate code. The biggest issue probably was for the library developers (Django, Flask, Jinja, pymongo etc) to create a new Py3 package. But now that most of the important libraries and frameworks have moved to Python 3, application developers could probably move along with the change. It's not that much work for the app developers.
The feedback sandwich is something to be avoided. People are generally predisposed to either hear positive or negative feedback, but not both. When you give sandwiched feedback, those that easily hear positive feedback will miss the negative and those that easily hear negative feedback will miss the positive. Almost no one will hear both.

Or so says the management training courses I've recently taken. Supposedly there's studies to back this up, too, though I've never read them myself.
IIRC, there's a setting for it on the phone, somewhere in the Messages settings.
I am not sure it will come to pass, but I would like to see the following features:

1. Email user and domain certification. For example, when I receive an email from john.doe@acme.com, there would be Email Certificate Authorities that would ensure the email was from John Doe and he works for Acme Inc. Or that johnnieD@jdoe.org is again John Doe and that jdoe.org is his personal domain.

2. Email archival services. These services would collect, store, and index email including all attachments. Would like legislation that would require all commercial Email providers to submit all of an individual's email to the archival service of the individual's choice.

3. Ability for email recipients to charge email senders an optional delivery fee. This will allow individuals to profit from being the target of spam email.
Some of this is frustrating to read. Architectural and detailed design decisions should be made and approved almost entirely before the coding of those features is started. (Obviously this is the ideal and not always possible).

This means that the code reviews should involve little more that a checklist of those approved design decisions against their implementation, perhaps a code style is verified as well.

Coding without a design is just hacking, which I believe is the primary cause of burn-out and should be avoided as much as possible.

So, the question is, do you have a design document? I know it doesn't sound very agile, but traditional engineering procedures, when managed well, have a lot of merit in controlling product quality and cost.
I could use the "nearby fire" one (building across the street that is prone to arson): what app are you using for that?
8 months of battery life, and talks Bluetooth. Someone got low-power right.
Great find. There's an archive of his posts on the eBay Tech Blog. Looks like interesting reading.

http://www.ebaytechblog.com/author/dgoldberg/
Thank you for raising this. My faith in humanity has been restored.
Needs more sounds that come from the left speaker. All I here are right speaker sounds.
This is so interesting, and especially frustrating (for both instructors and students) because really, most of the time only tenured faculty have the luxury of pushing back against the norm to really engage with students more outside of class and go beyond just being graders.
I think allocation is a discussion worth continuing. It's so intrinsic to the in-the-large error rates - overcomplicate the data allocation picture, and you end up writing more, slower, and buggier code, but only some time after you made the mistake. Any solution you can name only captures a fragment of the problem.
This paper [1] (thou it is a tad old now) shows that the register machine approach does still outperform the stack machine by a fair margin. Largely from the reduction of needed instructions.

Wonder which is a better source represntation for a JIT thou.

[1] https://www.usenix.org/legacy/events/vee05/full_papers/p153-...
As I mentioned above, collectively, the three of us have interviewed dozens of times over the last 3 years, so this is from personal experience.

I've personally interviewed many dozens of times over the last 20 years I've been in Silicon Valley. The expectations from interviews have definitely changed, especially after Google (I interviewed their twice and never made it past the hiring committee). At one well-known company, I went through 15 whiteboard interviews (3 different days x 5 interviews per day) and finally got the job. I'm not sure why I stuck with it, but I did.

If the nature of interviews have changed over the last year, I'll be thrilled, but I doubt it based on the reports I've heard from other friends of mine that have interviewed over the last few months.
A tutorial to use grunt-image-embed to convert images into data-uris
Send email notification of GitHub's trending repositories
I get the feeling that at some large companies there is the "front door", geared towards junior staff and fresh graduates, and typified by whiteboard coding trivia, and then the "back door", geared towards opportunistic hires of world class talent. Anyone else get that feeling?
I couldn't see the article, only the abstract. But what they report in the abstract is some regression coefficients for a "masculinity score" and associated p-values. A very simple analysis, and not much that can go wrong there.

My only concern is with cherry picking the chemicals. It wasn't clear if they were only reporting specific chemicals that had significant relationships, or if all the chemicals that would be expected to have a significant relationship did.
It'd be interesting to compare the speed with a Spigot algorithm (http://en.wikipedia.org/wiki/Spigot_algorithm ), which requires only faster fixed-precision operations instead of the multi-precision division he used; there's a very small C program here which does that:

http://wiki.tcl.tk/6636
Ha! I'm like that with my QA people, begging them to come after me with a blunt weapon.
Always easier to start as an individual. I managed to retrain myself over the years from being a cowboy coder.

Since I'm one of the lead developers, I just started practicing what I preached. Every new system I build has unit tests, and every time I integrate with a legacy system or another system someone works on, I write tests for it.

I also work with that engineer to see if they need to add tests on their end.

Anytime something written in the cowboy days in production breaks, I check if I should write a test. (Normally I need to.)

This way it spread "virally" from me.

For mass adoption among the team, try to get your test workflow down so it's easy to explain and pickup.
Ask HN: Will the Price of Bitcoins and Alts Skyrocket Again?
Hi,

I miss the days of $1k BTC & $15 LTC. I'm here wondering out loud if people think there'll be another rally like Thanksgiving a couple years ago. What do you think might cause another bull run? Or do you expect the bear conditions to continue?
If you ignore more than 9/10 notifications, your notifications should be more smart, not your watch.
visual basic was real easy to use. As long as you didn't want to program a complex game.
I accidentally pasted (L)GPL / CC-SA snippet my code, what do I do now?
Using Ethos, Pathos, and Logos to Design Effective Websites
Quick tip/Easter egg. Wrapping the text in parenthesis allows you to do triplets.
Great, he wants to steal. Two wrongs dont make a right.

There are plenty if people with that superpower, and it hasn't been a good thing.
No shit. The watch is designed to be charged overnight, every night.

Apparently he doesn't want to do that, because he wants to look at his watch on his wrist if he wakes up in the night.

So apparently the moral of the story is: if you don't charge a device that is designed to be charged every night, it will go flat.

This guy doesn't need a second watch, he needs a new fucking brain.
This is excellent, and a great reflection for what you'd be like to work with.
What is the difference between SocketIO and this?
IBM's Watson supercomputer strives to be jack of all trades
Which group are you referring to? Mainstream languages? The languages mentioned above? Perl 6 was designed from start to be very breaking, but even putting Perl 6 aside, Ruby had quite a few breaking changes going from 1.8 to 1.9 - and that was a merely point release.

Breaking changes are tough, but many libraries with a large codebase managed to update to Python 3 and even maintain dual-version support using compatible features, compatibility libraries and automated conversion tools.

For the everyday users things would be much simpler, and hence the main reasons for converting is not "too many breaking changes" but rather "not enough compelling changes".
It seems it's just a frontend to Microsoft OCR.

From the article:

The (a9t9) Free OCR Software for Windows Store tool is a graphical user interface front-end (GUI) for the new Microsoft OCR library. It is written in C#/WPF and the full source code is available as ready-to-compile Microsoft Visual Studio 2013 project on GitHub under the GPL V2 open source license.
So he is basically saying Jeff Hawkins was right all along. At least on SDRs
Agreed, it was a bit ungenerous, esp. b/c I didn't realize til someone mentioned it below that the author was a teenager.

My objection, though, is not what's above/below me, it's that given the title, I was expecting a deeper article only to find one that has appeared numerous times. It was frustration I was expressing more than condescension. But you're quite right in using the term "ungenerous." I appreciate the gentle reproof.
so from a logistics stand point if you have more drivers you would have more drivers closer to where I am and there for faster to pick me up and less cost. but is the cost so much less that it would stop an new entrant?
I understand where you're going, but this is not a continuation in the formal sense, and it isn't even usefully similar.

If the client stores the state on behalf of the server, the server will potentially be working with a modified dataset on the next request, and we're right back where we started with limit and offset.

You can cook up a scheme to make it work for a restricted range of requests, but the compromises are severe.
I've felt this way about all watches since my first mobile phone. If the watch were to replace the phone entirely I would be on board.
$1.4B revenue, with $0.577B loss, so, they spend $2B to bring in $1.4B; Not a good business.

We can't talk about a profit multiplier (Twitter has never had a single profitable quarter), but even if the $1.4B was all profit, a 17 P/E is not easilly supported.

In my opinion, Twitter has been a zombie for a while - there's no way they'll have enough profit to justify a >$10BN valuation, and that's only if they stumble on some revolutionary profit model. If they don't, even $2BN will be lucky.

Although what is likely to happen is that a stock market crisis will harm all companies, those with potential and those without. So Twitter will go down, "as if" for the wrong reasons, and the business model and its execution will not be found guilty (or not guilty).
The comment as written is perfunctory and has a dismissive tone - it would be more constructive if it went into more detail and avoided that tone. I'd also say it's off topic to some extent, since nobody has actually claimed that architecting an app from scratch in a combination of Go and Rust (as opposed to using existing {Go, Rust} code from the other) is a good design - although I can imagine someone might think it is.
In the same way that fax and letter writing still exist, email will always exist. We still don't have any other system for global personalized store-and-forward that is remotely transparent (ie. bigcorp-independentish), much less free.
The problem is knowing which 90% can be ignored...sure I can turn off all email notifications or only show emails from "VIPs" but sometimes I really do need to know that a downstream team has an outage that will impact me, and I need to know immediately to respond...
This is fantastic advice. I went software engineer -> sales engineer -> software engineer without any issue career wise.

Seeing the sales side of business gave me a very valuable understanding of how businesses work, which in turn has made it 10x easier to be a consultant for companies. It makes it much easier to talk to company owners who want to hear about the value I offer them and their business as opposed to babbling on about whatever cool technology I think I'm hot shit in.
Socket IO is a service, this is something you install on your server
I suspect that email is fine, but at present is fallong victim to an "engagement bubble." As newsletters proliferate, they will become less effective.
Not to mention the fact that besides the basic premise of the product, Spotify manages to be shite at nearly every bit of functionality they offer. Navigation, discovery, organisation, it's all awful. And now that they've dropped the API, there's no third party apps to compensate for it. It has that one killer feature, but sucks at everything else.

I'm sure the back end is technically awesome, but I really hope Spotify gets some competition from a party that actually cares about music and the user experience.

Spotify could be so much, much better. Instead they're just lazily exploiting their licensing advantage and what is effectively a monopoly. (Pandora isn't available where I live, nor in most parts of the world.)

(To be fair, half the mess the UI is is probably caused by pressure from the music industry to peddle their crap regardless of what the user actually wants. At least that's what I hope, otherwise Spotify is even worse than I thought.)
The three levels Tao lists (roughly paraphrasable as novice - master - true master) can be applied to many other endeavors, e.g. art, martial arts, programming, as other point out in other comments. What I'd like to stress is the damage that's generally done in going from Level 1 to 2 in math teaching.

As a specific example take Analysis, generally taught using Rudin. I took this course in my graduate EE studies and detested it. I later thought about this and came to the conclusion that the main reason was the manner of exposition in Rudin where the classical approach is used: each chapter contains an endless sequence of lemmas, minor theorems, etc., one after the other with no discernible purpose and at the end of the chapter you get to prove a big result by using all that machinery. This approach, which dates back to at least Gauss (commonly attributed quote, which I couldn't find the source: "no self-respecting architect leaves the scaffolding in place after completing the building") not only is backward to the real course of events, it sucks the motivation by being so. At least it did so for me and for some other otherwise intelligent friends.
If you name the methods correctly (what they do) splitting actually helps readability of the code.
It is quite hard to read and remember what was in the beginning of 500 line method.
The truth is that Daniel Ek met the major 4/5 labels at the same time and showed them their (at the time pirate) software. They said - yes - if we can own 75-80% of you. The truth is that the major labels own about 80% of Spotify between them - it wasn't the RIAA.
Telling time is <5% of my usage for my watch. My next appointment, current activity level, and favorite stock price are much much more important to me at a glance and no analog watch will tell me that.