skysight-inc/HackerNews huggingface dataset:
Thanks for the links, what I was actually trying to argue were two things, one was that the larger the data set the more homogenized and useless the data becomes, and two that looking at data for a given city returns different results.

There are lots of ways to come up with insights into what is happening, one way is to take the prices experienced by an individual in a single location over time, then to take the population of each set of locations and compute p(I|L) where I is your experienced inflation rate, give L your location. Then you can ask questions like "What is the likelyhood that a given individual has experienced an inflation rate that differs significantly from the reported rate? (either positively or negatively)"

Charts like http://www.city-data.com/ which can show you housing pricing changes by city for example you can see the wide disparity in changes between coastal vs more central states. Some states would have experienced very little change, others quite a bit. Now overlay that on population. Then you start to get to the answer of "What do 'most' people' experience in terms of inflation." The newspaper archive is a great way to check the numbers.

Thanks again for the links, one of the criticisms for the CPI scale has always been this : "The CPI follows the prices of a sample of items in various categories of consumer spending—such as food, clothing, shelter, and medical services—that people buy for day-to-day living."

Which historically did not include changes in quantity. So a 'can of soup' which went from $1.00 -> $1.25 over 10 years seems like it has a 25% increase in cost, but it went from 16 -> 10 ounces. Which means its actual cost went from $1.00 -> $2.00 when computing the per ounce price. This is another great thing you can see/check with newspaper archives as grocery prices are exceptionally well documented.
Bad review couple win compensation
> Perhaps one day providing the develop environment's definition in the form of a Vagrant VM (or, probably better, a Dockerfile) will be as common sense as providing README and LICENSE files.

I would hope this becomes a trend. I was very happy when Discourse first went open source and included a Vagrantfile for development in their git repo, made getting up and running much easier (especially since I'm running on windows a majority of the time and certain libraries don't always play nice).
Code can also stop manual errors from creeping in.

This spring, I put together a graphic novel. When I was creating the list of source files to drop into InDesign's batch processor (a tedious task that involved full file system paths to a bunch of sequentially numbered files), I left one out. I managed to miss the forest for the trees when proofing, and didn't realize I'd made this mistake until I was sitting down to relax and enjoy reading the advance copy. With 399 more sitting on a loading dock waiting to be shipped to me.

I had to do a new print run; this cost me about $6000, which pretty much puts the Kickstarter for this volume in the red.

I also wrote a simple little script that I can point at a directory full of files, and get a CSV of everything in it to feed to InDesign. I will not be making this particular mistake again on a larger project. There will be other ones, I'm sure. And I'll try to find ways to automate stuff I can, and improve my proof reading process as well.

You are going to make mistakes. By hand, and in creating automated systems. This is a fact of life.
> everything you build 'the best way' will become awful coding practice in a few short years

Disagree.

Good architecture is almost timeless. It isn't always en vogue, but it is recognizable by being pleasant to maintain, conceptually cohesive, and simple. It usually resembles a domain model, with the UI, persistence, and everything else being built around it.

It is a force at least as strong as the language used.
Just guessing / offering personal opinion... such words would rarely make sense in source code.

What would a function called "believe" do?

I can imagine such function names in, say, artificial intelligence projects, but even there used (probably) in a loose way. I suspect few web applications or iPhone games or flight control programs would be doing any "believing", real or imaginary.

Of the words you suggested, "sense" seems most likely to appear in real use, as robotic software and such may be literally accessing sensors.
Yup, in the canadian forces, they call it 'Duty Officer', much less glorious sounding than Battle Captain =)

I think the best way to make a difference with software would be as a consultant, deploying with units and doing work straight from there, in an ad-hoc way. Similarly I guess to the stories about how the Obama elections team worked. Deploying a small group of devs with a battle group, who have for purpose to write custom software to make the battle group more efficient. By participating in the pre-deployment training and exercise, the devs could familiarize themselves with the most important tools that need to be created for the deployment. Then while deployed, polish the rough edges and adapt the tools to new situations.

Otherwise, going through the procurement chain of the army will inevitably lead to insanity and bad software, and no actionable result. We had software when I went about writing those tools; it was just so bad and inappropriate that nobody used it.
What I found interesting is how different it is from the idealized picture of a chaste moral past a lot of people would like to believe in, and how different societies can treat the process of sexualization.
They are all listed in the man page, thankfully.
A Second Look at a wooden bench
I think the problem is that we are talking about two different things.

The very start of the paper describes the term and it's methodology (which is what we are discussing), and then goes on to explain googles own implementation using GFS (which you seem to be getting hung up on.)
I generally recommend that new devs who don't yet know what they want to specialize in learn front-end dev first and then work their way backwards.

The reason is that frontend skills are widely transferrable between companies, and qualify you for a large number of jobs. This means that you can get your foot in the door at a lot of different places, and if you don't like it, you can switch to another company or product really easily. Once you find a specialty, then you can start learning backend technologies in depth, and probably switch roles within the company.

Backend technologies are often surprisingly tightly tied to a particular problem domain. Yes, familiarity with SQL and an RDBMS will help you in a lot of places. However, many of the more interesting places to work need graph databases, high-performance timeseries stores, memory caches, bloom filters, flat file formats, and a large number of custom technologies.

And when it comes to data analysis, your effectiveness is largely dependent upon how familiar you are with the particular data set you are analyzing. I saw wizards work wonders with Google's corpus of news articles; they could really quickly machine-learn models from the corpus, even for totally new products, because they'd been working with the data set for the last 10 years. However, while there are some general techniques that most data extraction & prediction problems use, that wizardry wouldn't translate to, say, protein folding. Backend data processing is much less transferrable between different sets of data.

The flip side is that domain-specific knowledge tends to last much longer than frontend technologies. Typically, you have to learn a new frontend technology every 5-10 years; I started my career in 2000 and have already had to jump from Java Swing to static webpages to single-page webapps to mobile technologies.
What are the advantages of this library over browserify + browserify-middleware ?
The dilemma of polio research: amelioration vs. cure
While a good post, the real issue is that non technical managers of technical projects is quickly becoming more of a risk than many projects can prudently accept.

The old, and unfair, characterization of programmers as smelly trolls that can't handle client interactions is more of a crutch for fools than a reality.

The truth is my clients complain bitterly about how they'd prefer to just talk directly to the dev's and not be bothered by the various hand waivers trying to justify their line item on an invoice. Often this is a great way to annoy the dev team, but it's a good expression of the perceived value of a non technical intermediary.

In the end the old truism of "You can't manage what you don't understand" still applies to this new fangled industry of software development.

That being said, ramping dev's up on management techniques is another challenge, for another internet rant.
So no one has mentioned this yet, but this article is actually the Fortune cover story.

And I think very much deserved, not for most of the details mentioned in the article, but because of their pricing page: http://www.theranos.com/test-menu -- it's freaking cheap.
I had a smile on my face while reading this article. Regardless of the PR behind the article, it's certainly refreshing to see a startup like this. I'm rooting for them. Medtech needs game changing technologies!
Show HN: Entropass
I know its all highly secret, but how awesome would it be to read Bill Gates's take on the technology?
I've always loved KDE and support everything they're going. Good job team!
Preview: LinnStrument
quite realted, but dont know how this would fit in there: DONT PANIC First Aid Kit - resources and links: https://8ack.de/firstaidkit/
Neat idea, but that website needs some serious contrast. Almost unreadable when scaled.
> she started her first business while still in high school, selling C++ compilers to Chinese universities.

Along with the rest of the weirdness being mentioned by others, some of this really doesn't begin to make sense to me. o_O

Custom compilers have been a thing a few times in the past, but in the late 90s, what possible reason could there be for this?
Well, if we start treating domain names as a public resource, then caps might start making more sense. It's like any other regulation.

AFAIK, there are regulations already for how much you can pollute your environment, usage of rivers, height of buildings, rearchitecting your house etc.
SPF: A JavaScript framework for navigation and page updates from YouTube
Not that it matters but I think this is built using Reactjs.
About a month ago I got an old slide rule from my Grandfather that he'd used in engineering school. It's a little thing, but it's amazing to hold something that was some decades ago the standard tool for certain types of computation. It really puts into perspective just how far we've all come in such a short time.
This is really awesome. And the search bar works well!
No - the Supreme Court has not ruled on any of the NSA's recently disclosed programs. So they haven't had the chance to say whether they're searches.

And on that threshold question of whether any NSA surveillance programs are "searches" under the meaning of the Fourth Amendment, the Supreme Court would ask if a challenged program violates American citizens' "reasonable expectation of privacy." Much in this opinion would be directly relevant to that question.
Exactly. The React paradigm is to never mutate the DOM directly, but instead let React mutate it. I wrote a friendly intro here: http://blog.reverberate.org/2014/02/react-demystified.html
Marcel has made his feelings on Swift clear: http://openradar.appspot.com/17180612
I recently started using Giraffe as a dashboard for RUM performance data in my job. Good job man, thanks.
Akka Clustering, Step by Step
Do you have any links to relevant discussion, documentation and/or code related a (official?) pid 1 process for/by docker? I'm not able to find it quickly and I thought it might be useful if you could share given that you clearly have some context. Thanks!
Interesting editorial decision by Jeremy to submit this today and "The Fallacy of Tiny Modules" a few weeks ago. I recommend reading both.

http://hueniverse.com/2014/05/30/the-fallacy-of-tiny-modules...

https://news.ycombinator.com/item?id=7822383
Ask ten PMs what they do, and you’ll get ten different answers. Let's fix that.
I'm excited to read this, I just bought a copy.

I'm presently debating between using Haskell or Clojure for data analysis here at work (or most likely some combination of the two), so the timing couldn't be better.
FIFA World Cup Security Team Reveals their Wi-Fi Password on Twitter
Agreed. I say that as a tech geek and as someone who, unfortunately, is a frequent and regular blood-test patient.
If you're in a car, yes you do. A license plate - and these scanners are all over the place.
Ask HN: Your home server/NAS set up
I'm looking into upgrading my Netgear ReadyNAS duo to something with more HDD bays (>= 4) as well as something more flexible to aid my move away from the cloud.

My main requirements are:

- A backup destination (timemachine/rsync)
- A shared file storage space
- Run a development environment (web development)
- Ability to run a few other servers; gitlab, media, torrents

I was thinking of getting a HP proliant server and running freenas or something similar but the cost stacks up quite quickly. The alternative is to go with a more powerful small-office NAS.

What do people here use at home/small office?
FWIW, Vundle doesn't use :BundleInstall anymore, it's :PluginInstall. Similarly it's Plugin ".../..." instead of Bundle ".../..."
Can I upvote this like a million times?
I think you're taking this far too seriously. It is a little bit of fun both on Google's part and on the part of the people who will make/get a Cardboard.

So what if some people have a little bit of fun? Nobody that I've read claims it is the next big thing or it will somehow replace Google Glass or any other VR-like solution.
why not just create a vpn between the nodes with another private IP space and send your data through that?
How this pill helps you lucid dream without the training
"You import someone's changes to a local notebook" <-- there are no existing tools that reliably automate that. (I'm aware of the notebook diff utility in the AuthorTools package, but that's not reliable). There are many tools if you're working solely with plain text.
And a lawyer in OP's specific country, not an internet lawyer who might know nothing about specific local laws.
Dropping features, dropping IE8, adding features, rewriting the whole library, etc :p.
Seems rather sad state of our Patent system here in the US where a 19 year old with no prior technical background, who was a Chemical Engineering student, a sophomore no less (meaning barely finished or finishing General Ed. requirements and just starting Major courses), can write and file for a highly-technical patent involving radios, sensors, embedded devices, and the like.

> And we could put a cellphone chip on it, and it could telemeter out to the doctor or the patient what was going on.

It's very doubtful she understood how any of that works, or would work in her product/patent.

Underlying story seems it's absurd this was patent-able.
Indeed -- https://github.com/divad12/vim-awesome/pull/17

Thanks for pointing this out to us. Will merge when I get home.
"opinions are like assholes, everyone's got one."

You bore me.
You could make it free for up to 2 habits.
Sure, once you're already in a relationship, it's not good to apply that label. But how many people do you know that are: {vacuous, boring, self-centered, naive, capricious, overly sensitive, insensitive, uptight, etc}? These are characteristics we gloss over when we first start dating in favor of characteristics we like (attractive but vacuous, exciting but self-centered, funny but overly sensitive). But over time those flaws become more apparent. That makes it harder to be kind to someone you've been with for five years than to someone you just started dating.
Yes, thats my fault. Whats happening under the hood is searchcode is trying to match "MongoDBObject find" exactly, where as Github is going for a looser but phrase heavy search.

Its something I am going to change based on feedback as clearly what I am doing is not what people are expecting. I will however make it an option, so you can chose exact match (current) or loose.
I generally agree. This decision had everything to do with flexibility and composability of individual modules, not file size.
It's worth noting many believe excessive military spending was a key factor in taking down the Soviet Union.
Ouch. The bug here is simple. The LZO format has a block type for uncompressable data ("literal runs"). LZO implementations (all the ones Don Bailey looked at) keep a counter associated with literal runs that count NUL (00h) bytes. The counter can be made to grow quickly and eventually overflows. The LZO codecs Bailey looked at use that counter for a copy, and thus have a memory corruption flaw.

It's likely that anything you use that decompresses LZO (MPEG files are a good example) uses C code to do it, and not code in a higher-level language.

So you'd want to know any place your application accepts a file format that can use LZO, because that might be a potential memory corruption flaw in your application regardless of the language you built it in.

Memory corruption flaws are very bad; these are the bugs that often result in attackers being able to upload code to your server that is then executed. That vulnerability, once triggered on your site, is probably game-over for your whole data center/deployment environment.

This flaw won't be as easy to exploit as the Rails YAML bug will be, but to the extent that your code reuses a well-known LZO codec, there may be shrink-wrap exploits available soon.
Tagging along with PHP – A journey from 1998 until today
Of course. It's a promo stunt to get headlines, not an actual service. Wait and see how suspiciously young and attractive all the couples will be.
> The main blocker to this easy migration was that Facebook’s private IP space conflicts with that of EC2

IPv6 adoption could not happen soon enough.
App Store Optimization: Selecting the Right Keywords
All we have to do is get all certs flagged with must-staple and have all webservers handle stapling, and we're set!

(Sarcasm? Moi?)
Any plans for a Kindle or other ebook version? This looks like a fun presentation of an interesting topic, but I'd love to read it electronically on a laptop so I can try out the examples.
(I'm the SSL co-op guy)

- Probably in Australia, at least at first, since that's where I'm based. I'd like the DR site to be in Europe, if possible, but that might not be a day 1 achievement.

- I'd like to be able to issue certs from day one of the co-op, via a reseller or other arrangement -- that might cost a few dollars per cert, though. It's a minimum of two years from "let's do this!" to being accepted in all the browsers, though (look at the Mozilla inclusion timeline for an idea of best case: https://wiki.mozilla.org/CA:How_to_apply#Timeline)

- An API is definitely intended from day one. My general architecture for these kinds of systems is API for everyone, and the website just talks to the same API that the general public does.

I'd love to talk to you more about how the co-op could help you with your system.
Perhaps that would become a bottleneck at Instagram's scale?
Ask HN: Linux based micro server for firewall
I'm fighting ipv6 issues with an older Sonicwall TZ100. I am longing for the days of setting up my firewall with iptables and am starting to think it's time to give this thing the boot. They want me to buy new hardware to support ipv6!

What micro server would people suggest for a firewall? I need at least 3 ethernets (WiFi, Wan, Lan) and would love four like the TZ100 has.
(disclosure: I'm the SSL co-op guy)

All of Google's free services (CDN, DNS, Chrome, etc) are centred around improving the experience of using the web, so more people use it for longer (and, hopefully, do more searches with Google and/or visit more webpages with AdSense ads on them). I'm not sure how more SSL-secured traffic feeds into that, exactly, but if anyone at Google wants to talk sponsorship, I'm all ears...
Looking forward to KDE apps not dragging hundreds of megs of dependencies. And though I don't use it anymore, I still have a soft spot for this DE and the amount of flexibility it offers. Now, if it was a bit less buggy...
Is neti open-source?
Exciting to see this, but it's painfully clear how much work there is to be done for Haskell to be a competitor to, for example, what is available in Python.
Smoke Tester : Post Deployment Testing Version 0.03 Released
>Thousands of startups have launched and failed precisely for the lack of quality.

That was an emphatic statement in the article and I feel the discussion would really be constructive if the author (or posters in this thread) listed concrete examples of startups that failed primarily because of software quality.

If success has many fathers, failures are not orphans and also have many fathers as well. Perhaps software quality was not the 1st but actually the 2nd or 3rd reason why the company failed. I'm not saying such examples of software execution killing the company don't exist. I just can't think of any prominent examples at the moment.

I'm leaving out poor software examples such as the Atari 2600 E.T Extra Terrestrial game cartridge because that was not a startup situation.[1]

[1]http://en.wikipedia.org/wiki/E.T._the_Extra-Terrestrial_(vid...

On the other hand, an internet company like Friendster looks like an interesting case study. Their infrastructure software was not efficiently traversing their social graph. It was something Facebook programmers conquered but Friendster did not. But was software quality the #1 reason behind Friendster's demise? Apparently, the board-of-directors didn't prioritize and throw money at the engineering challenges that Friendster was facing.[2] So the their failure can be reinterpreted as a combination of management of priorities and software execution. Maybe if they did throw money at the issue, it wouldn't have mattered because their programming staff didn't have the unique competencies to tackle at-scale social graph problems. In that case, it's not a "technical debt" issue but a "hiring talent" issue.

[2]http://highscalability.com/friendster-lost-lead-because-fail...

Another case study might be the Chandler software (chronicled in the book "Dreaming in Code"). However, it appears that the product got bogged down by architecture astronauts unable to make decisions and not "technical debt".

If there are thousands of companies that failed on software quality, it'd be interesting to see which ones can be disentangled from non-software issues and we can confidently say, "yep, that technical debt is what killed them."

(My curiosity for real examples does not mean I'm endorsing technical debt. I'd just like to get some real-world perspective on this topic.)