skysight-inc/HackerNews huggingface dataset:
>inability to acquire new stuff or inability to focus due the large number of associations running out from each thought you have

It's exactly this. In the active mind (hyperactive, perhaps), the dataset is ever increasing and the memory banks are thrashing. On the best days, the cache is very deep. You never really know how deep the cache goes, though, so what might be the in L3 one day silently becomes /dev/null. This is a problem. (It's also, as you point out, a blessing)

A permanent store is the solution, but the brute force (write everything down) doesn't immediately solve the issue. There is no metadata in writing, so searching through papers involves full-text O(ludicrous) kind of searches. Every permanent store needs an index to be useful. It looks like the author has developed an extensive, coherent(?) way to colocate and index written information.

Considering how slowly most people can write, I'd be very curious to see how good mapping software could be used with ~300wpm stenographer-paced typing (Plover). Typing as fast as I can think into a searchable, sortable, arbitrarily small/large/nested/rearrangable/duplicable/etc medium is intriguing, to say the least.

EDIT: One more thing. The 'immobilization' that some ridicule is inherent in the medium: ink on paper. A written page is immutable and cannot show a diff. This is a bit like Purely Functional Data Structures. The 'structure' is at best just a single page, rewritten fairly quickly. As the ideas grow, sheet by sheet, editing a single page requires rebuilding the now-12-page idea. This is refactoring with pen & paper.

The only way to be 'mobile' is to either not write it down in the first place or to archive and never look at again. You're right in that rehashing old ideas thwarts gc: it's like burning an image into your screen, right into the phosphorus.
TBH I preferred this story when it was an Onion article: http://www.theonion.com/articles/two-hipsters-angrily-call-e...
I'm pretty sure that if you asked your developers point blank if they'd like a nice office with a door, they would.

If you asked any developer who has actually had an office at a previous job, and I'm 100% sure they'd be in favor.

Young devs that have never dreamed such a dream might think they don't care. But they'd be hugely more productive in an office.

It is the same thing as having a big monitor for your laptop. Once you have it, you'll just feel so unproductive without it. With an office you can just get in the zone and stay there as long as you like.

With pair programming or discussions, you just pick one of your offices and shut the door. I found myself collaborating more in offices, because there is less worry about disturbing others. (Or the cognitive overhead of getting a conference room.)

By being in the open plan yourself, you're sending a strong message that there is no way offices will be tolerated, so there isn't any point in asking.
Hey Dan, no question just a small gush: this is one of the best KickStarter campaigns I've seen in a while. The video is great, it's fun reading the story and seeing the extra content, and I think more toys like this should exist in the world. I don't have kids but I feel excited about it anyways - best of luck to you!
AeroFS is hiring Senior Engineers, iOS Engineers, and Front-End Engineers
Have you used QtQuick (particularly the QtQuick.Controls package) in Qt 5.1+? Because based on what you wrote I believe it covers a lot of what you're asking for here.
Clickable links:

http://d.pr/i/53NF | http://d.pr/i/AxF5 | http://d.pr/i/TJwF | http://d.pr/i/aN40
And no use in leaving them open as well. What would a new answer buried away accomplish?

And closing them with the "historical" note makes it clear that similar questions should not be asked.
Cucumber doesn't mean anything. Sinatra doesn't mean anything. It's no different of a situation, except my clients would look at me like I grew a third ear if I made any mention of them.
Shadowbans are abused all the time in Reddit, for example. Not the sitewide sbans, but the ones done using AutoModerator, where they delete your comment with no warning, and you don't find out because you still see your own comments.

/r/Games for instance, has a policy of arbitrary banning people this way.
Exactly. Same for non-commodity hardware. Come to think of it, even true for commodity hardware.
How I Manage my Freelance Finances | theAdmin
Nor a properly documented procedure seems to exist for random people (me) to report blatant PCI-DSS violation they stumbled upon.

PCI-DSS is barely better than security theater, with so litte effort spent on finding violations...
Anyone know how many UI bugs were reported or seen with previous iOS versions? I'm just wondering if this is a usual part of each major iOS rollout, or a unique instance.
"Eat the frog" is an interesting concept: "Wake up 45 minutes earlier and work on one of your big action items."

It's so easy to get bogged down in day-to-day tasks and not focus on moving your product / business forward. Often, all it takes is 30-60 minutes of focus a day to really make some progress.
Yes, where can I sign on?
Hipster-hate strikes me as just another thinly veiled form of bullying, and it's interesting to see how readily internet nerds - the people who are disproportionately to have been bullied in the past - engage in it.

Look! He's different! Let's make assumptions about his motivations and get him!

It's also interesting to see how many times Reddit (and other communities) fly into a rage-fest because of lack of context, only to make an about-face when the full picture comes out. It's also interesting how no matter how many times this exact situation happens, there is no stopping the next rage-fest.

Above all other things, internet communities is what makes me cynical about humanity.
Yeah, that's like saying Python sucks for scripting because all your work in the REPL won't be saved. Goes both ways.
I drank the Cucumber Kool-Aid and had an app with basically 100% Cucumber coverage. If I wanted to change something, I would first write a cuke for it, write specs as necessary, and only as necessary write actual code.

Of course I got into the same spot that almost everyone gets into doing that: too many "and then I click..." scenarios. Great coverage, but then the requirements change substantially and the test base is just a massive snarl of interdependent assumptions. At one point I had effectively written, in cucumber, a natural language interface to my app.

But then at some point I needed to move and I needed to move fast and I just let the whole infrastructure rot. Now I'm doing almost everything on the client side anyway, so it's all a little moot.

All of that being said, I'm still a Cucumber fan, but I approach it differently. Here's what I think:

You should have cukes for the 5-10 things that if they don't work make your product completely pointless.

On Gmail, there would be cukes like:

When I receive the email from Fred about dinner
And I open it
Then I should see the message
When I reply
Then Fred should get my reply

And those cukes basically don't need to have wildcards:

When /^I reply$/ do
click "reply_button"
fill_in "message", :with => "I'll be there!"
click "Send"
end

Essentially:

* Use cucumber as a way to force you to keep track of the handful of absolutely critical integrated experiences

* Don't use fancy grammars... Think of steps as human-readable function names.

* Don't do anything fancy in the steps. They should just be a list of actions that users would have to do.

And yeah, there's no reason you couldn't do all of this in Steak. I think Cucumber is just nice in that it encourages you to write it out in human terms.
Cyber bullying kills kids. That's one thing to remember about all this. If he had been a shaky, insecure, frightened teen, this kind of treatment can push mild depression into thoughts of suicide. And many adults are also vulnerable to this kind of abuse. If you see this happening to anyone, please, step up and defend them.
This is one of my favorite quotes:

"The more you know who you are, and what you want, the less you let things upset you." -Lost in Translation
Or better yet, use make.
It's been a while since I've played games like this, but if I could just point my modern browser to a URL, subscribe for a few bucks a month, and start playing, I might just start again.
I was expecting to read something about Christian Weston Chandler. That guy is an object of internet ridicule like no other.
I don't quite see the reason for this with the cloud. Amazon has a whitepaper on AWS with HIPAA and I've seen some startups give presentations about their implementation in the AWS conference.

There's some misinformation on your website, "HIPAA compliance is costly and hard to get right" It's not. It's almost cheaper to sign an EA with Microsoft and use Azure (who by the way also sign a BAA) than your pricing. I also couldn't find any mention of what redundancy you use or any mention of uptime.

HIPAA compliance is basically encryption + access control + logs + redundancy with a few other simple features. All of which are easily accomplished with AWS or Azure. BAAs between you and your hosting provider are not necessary unless you have access to the PHI (Amazon doesn't, Azure does).

The biggest red flag to me is that this doesn't (as one might assume) absolve the developer from liability / responsibility. If it were to come to light that your business is (I don't think any of these things about you) corrupt/poorly run/hacked/breached/etc. the developer is then liable to immediately remedy the situation which may include being required to move elsewhere. That would be a huge disruption to any service as they would have to build a system from scratch while somehow still operating. This would be the only reason I would switch my apps from AWS to your service but unfortunately this is not the case. The fact also remains any HIPAA violation would be more likely in the implementation of the webapp (i.e. allowing images to be cached) and not in the storage of it. Leaks of encrypted PHI aren't even an issue with HIPAA.

You have the issue of being new and without a reputation while I can still be liable for your mistakes. While you have insurance it's not really feasible to sue someone as a startup. Anyone not a startup would find your pricing way too expensive.

Amazon whitepaper: https://aws.amazon.com/about-aws/whats-new/2009/04/06/whitep...
re:Invent presentation: http://www.slideshare.net/ControlGroup/aws-reinvent

TL;DR: BAAs do not remove liability, HIPAA compliance isn't nearly as complex as other regulatory bs, AWS and Azure are both easily made HIPAA compliant.
Nice post although I disagree that 30 years ago stuff mostly worked. That's not how I remember it but I guess his main point was that there was a lot less software then.
Yes, I have just noticed. It will be really great if you will make pull request of version which is compliant to you old version!
Keep in mind though that (according to Odersky) Scala's data structures are based on an improved version of Okasaki's research.

It's still very much a mind-twisting and expanding book though!
3753 Cruithne
Also be sure to check out http://nesdev.com/
Charles Carreon finally quits fighting, calls Oatmeal battle “a dumb thing”
Kruskal's Algorithm for Minimal Spanning Trees
> We love Apple.

Stopped reading there ...
Yeah, Midland Radio (no affiliation) also makes a slimmer action camera called the XTC: https://midlandusa.com/xtc-cameras/

GoPro's brand definitely doing that Kleenex thing where it's just the word for a small tough camera.
Some of that must be a California thing.
In an European office of one of the mentioned companies, most people almost always eat lunch with their team in a canteen and plenty people do 3-4 day long weekends to go on trips all the time (+ normal 1-2 week long vacations of course). Yes, sometimes I go online during my vacation or when travelling during the weekend to perhaps look at emails or do some simple work, but that is because I'm motivated - nobody is making me do it.
Startup School 2013 Speakers (Updated)
Thanks gbelote! Nice to be able to give something back to the HN community, which was helpful in figuring out how to do Kickstarter right.
Coinvoice: Invoice in USD and receive BTC
I understand your concern, but these days, cloud or no cloud isn't what's important, just that you use a data store in a HIPAA compliant fashion and that the provider will sign a BAA. Health tech startups these days are using AWS, Azure, and Rackspace, all of which will sign BAA's.
To the people who are saying that this will only be for the rich: I would like to point out that we already spend over $500 billion on Medicare. In other words we already spend 10 times Google's yearly revenue, half-assedly patching up the symptoms of the disease that every single human is already afflicted with, and we do it for everyone. If they actually solve this problem, it won't go only to rich people, because of the amount of money that buying it for everyone will save everyone.

(Yes, some problems might come in if they invent something that can keep you young if you start at 30, but doesn't do anything if you start at 65, however the long term benefit would still be amazing and maybe make the Republicans' dream of getting rid of Medicare finally come true...)

To the people who say death is natural: Many, many natural things are bad (high child mortality, smallpox, etc.) and many artificial things are good (antibiotics, vaccines, the computer letting you read this comment.) Naturalistic Fallacy.

To the people who say death is good: No it's not. My parents had me when they were older. Now my dad has a kind of cancer that is associated with aging (multiple myeloma.) He was diagnosed my first year of college (luckily he has been doing rather well considering for five years now.) I get to look forward to loosing him before I turn 30. I don't care why you think death is great because of its benefit to society; I don't want to loose my dad. Also, my kids will almost certainly never know their grandfather, just like I never knew mine (He died of the same kind of cancer a few months before I was born,) which is sad. You are severely underestimating the value of not having to watch people you care about shrivel up before your eyes and be irrevocably destroyed, knowing that there is nothing you can do to stop it.
As part of the internet generation, I believe the opposite to be true. Hence the widespread popularity of 2g1c
Yep, all of the action you see runs in a browser -- except for the console command that uploads assets to the CDN.
Could someone add (2012) to the title?
5 days to decide whether you're ready to found
A suggested checklist of things to do before you decide to go all-in on your startup idea.
Qt5 (the one the Go support is linked against) is already much better at that, and there's further work happening both upstream and in Ubuntu.
See the story of the person who broke down crying at an interview, from last week - https://news.ycombinator.com/item?id=6389293
I deleted my comment before you replied, because while I tried not to made it rude, I decided there's no reason to add another negative voice to this thread.

The fact is that Docker is very useful, but it really is simplistic from a technical perspective. It's a front-end that leverages the very impressive and very hard work done to create Linux, LXC, Aufs, etc. Those guys deserve 98% of the credit that Docker is getting, which I admit does irritate me to some degree.

Yes, Docker is a high level abstraction that could use OpenVZ or something else, but if it used OpenVZ I'd just say that the OpenVZ guys deserve most of the credit -- having done most of the hard work.

Docker is the kind of thing that companies create internally all the time, the way you did at dotCloud. It's very neat that you open sourced it, and that it has brought attention to another way of doing application deployment, but that doesn't make it a revolutionary technology.
I don't remember such a thing. If it was, it was brief. For the longest time, smartphones ran Symbian, PalmOS, Blackberry, or Windows Mobile (order varied by year).

Android phones largely took marketshare from the above. The original 2006 prototype looked largely like one of the devices above (mainly the blackberry) [1]. It was only after the iPhone that Android pivoted hard towards away from embedded keyboards.

[1] http://www.pcworld.com/article/254539/original_android_proto...
IDK about Eclipse, but Emacs comes with M-x artist-mode
HIPAA, unlike many other compliance standards, cannot be "certified." This can lead to certain levels of open interpretation, but best practices are generally agreed upon.

Products like TrueVault provide excellent value, but security awareness training is the golden key to improve an organization's information security posture.

For an example of what I mean, consider the following scenario:

- Patient data (called Protected Health Information, or PHI) is stored securely in a TrueVault database. This database is accessible only from the hospital, and TrueVault has signed a BAA with the covered entity.

- A surgeon is prepping a kidney transplant for patient John Smith. The surgery is tomorrow morning, and Dr. Goofböl wants to make sure he's familiar with the patient's medical history.

- Dr. Goofböl, an authorized viewer of this patient's PHI, accesses the data and begins to take notes. A new batch of PHI is now being created, as it contains medical information as well as identifying information of the patient (say, his name).

- Dr. Goofböl emails this document to himself (whether his work or personal email address--it doesn't really matter), and goes home for the night.

- Dr. Goofböl stops at a nice coffee shop on his way home, and his personal laptop (without full-disk encryption) is stolen. The data is lost, and cannot be accounted for.

My company provides HIPAA Security Risk Assessments, and I've seen this exact scenario play out many times, albeit with other "HIPAA compliant storage" solutions, rather than TrueVault. There is absolutely a place for secure products like this, but security awareness training and the true gravity of identity theft and information loss needs to be ingrained in the medical industry.

"Security" for a hospital used to mean protecting doctors and patients from intruders (or mentally unstable patients). It used to involve burly men in white clothes; they're not used to thinking about where their information is traveling. Furthermore, the government is mandating that electronic health information be available to patients through web-based patient portals, which introduces a whole different level of potential vulnerabilities.

I truly believe that the healthcare technology industry is going to be one of the most booming sectors of the next decade, but there are major changes that need to occur to facilitate that. Hospitals need better IT infrastructures, more attention needs to be paid to security, and better tech personnel need to be brought into these environments. Only then can the next generation of healthcare technology truly succeed.
LOL, I haven't. Thinking about a dev wearing those on top of noise reducing headphones is a pretty great mental image though. :-)
Cool. Are there any open issues where those of us who are interested can follow the details?

My main question is whether this will require users to create a fixed-size filesystem for each container up front, like you would have to do if you were using LVM snapshots directly.
NSA Gets it's Hack On
An interaction designer applies for a job at Campaign Monitor
looks good, the thing i dread with higher sales is getting calculations wrong and ending up thousands in the hole, but i guess there are ways round that :)
Looks like this could be useful, if the app supported multiple apple id's it would make managing multiple accounts a lot easier than using the website.
> If most people have the idea that your hammer is actually a screwdriver, it isn't their fault for misusing it.

Its not my hammer (or that of most of the people, I would imagine, posting in a similar vein), and I'm not interested in fault.

> Someone put that idea there

Yes, people have put out bad ideas of what Cucumber is for -- and the people complaining about it not being good for things it isn't designed for are among those people.

That's why some of us are countering those incorrect ideas, so they don't keep spreading.

> you as the creator of this not-a-screwdriver are responsible for the failure of that message.

Wrong ideas that only some subset of the people exposed to a product get about its use are not solely the responsibility of the creator of the product. Obviously, if you have an interest in selling the product, you are the person that stands to gain or lose based on those wrong ideas and you have a particular interest in correcting it and a responsibility to your business to take any efficient steps to combat that misimpression, but then again, if you are using tools in your business, you likewise have a particular interest in identifying and correcting your own mistaken ideas about tools and a responsibility to your business in taking any efficient steps to correct misimpressions you may have.
To add to the discussion/close the loop:
http://www.reddit.com/r/TrueReddit/comments/1mp79c/i_am_an_o...

Having been on Reddit for more than 6 years, what always blows me away are these "lessons". Sure, everyone backpedals a bit and thinks, "gee, he's not the douchebag hipster we thought and we acted like assholes" but it happens over, and over and over.

As others have also mentioned in here, I'm always amazed that those most prone to being bullied seem more than okay taking on the role of bully online with zero context.
I tend to agree with you that partitioning the market into two tiers ("junk" and "premium" in particular) is an artificial distinction but I disagree with your characterization of the iPad mini as something from the bottom tier. It is a different form factor, but that isn't the same thing as lower quality or less featureful.

Apple isn't afraid to use form factors, feature sets, and multiple SKUs to partition the market it is just that they focus on partitioning the upper-end of the market and not the entire market.

I wonder if Apple could ever manage multiple brands to partition the market even further in the way that Gap Inc, partitions the clothing retail market via its Banana Republic, Gap, and Old Navy brands.
Previous discussions:

https://news.ycombinator.com/item?id=4764864 (2012)

https://news.ycombinator.com/item?id=4763484 (2012)
Towards the end, he says "...but I do enjoy the Gherkin syntax. Not for testing, but for gathering feature requirements..." and this is where cucumber or fit or FitNesse is useful - you gather requirements, then because these requirements can be run as tests you start running these requirements as tests and now you have a living document of your product and product owners can read the tests (which are the requirements).
If you look at such tools as mere test runners, then they do add an extra layer of complexity, but these tools were not meant to be just test runners... so you are using it for the wrong thing... :)
Hell of a lot of absolute declarations ya got thar, Professor Wainwright.
Thanks hga! That's great feedback. I have very little artistic skill personally, so it's really rewarding to be able to bring this stuff to life.
> I liken Docker to a high level language

I like this: Using LXC directly is like using a (pointer, length) struct in C. Using Docker is like using an array-slice in Go. They're not that far apart, but they're on different levels of abstraction, and come with different guarantees (even if those guarantees might not, in practice, be enforced yet.)
I'm still surprised there is no SVM implementation for Mahout (http://stackoverflow.com/questions/10482646/recently-svm-imp...).
Well they certainly look cool, but a DNA analysis might be nice...
Hey Dan! Congrats!

Do you think you were able to get most of your press because "teaching code to kids" is so trendy right now?

Would you advice other Kickstarters to look for similar trends?