skysight-inc/HackerNews huggingface dataset:
Yeah, that's absolutely the point of PaaS/IaaS things. The point of Dokuen is to be able to deploy those things in a similar environment that is strictly under your control.

My use case, specifically, is that I have one app that has a large amount of personal data in it, and another one that doesn't fit under the terms of use of any of the PaaS providers. They're not going to get any traffic outside of me and a few other people and it's totally fine if they aren't available from time to time.

By using Foreman and Mason in my own environment, I get to use the patterns that those tools provide (buildpacks, Procfiles) outside of Heroku.
Remotely vibrate a phone with morse code using web sockets and the vibrate API
TalkDesk puts your company call centre in the cloud
Swapping is a different aspect of virtual memory.

Instead what we are talking about is having each process appear to have its own memory address, where virtual addresses are translated to different pages that may or may not be backed to specific physical RAM.
"Knowing how to code a mergesort" is specifically not what they're looking for, in my experience. The idea is to come up with a problem that requires an interesting algorithm that very few people will know, and see how the candidate reasons their way to an answer.
Sidecar app: A closer look
No, it isn't "as cheap as chips."

I've looked, and I can't buy it at any price, which means it's basically infinity. (Searching Newegg returns this: 'We have found 0 items that match "memristor".') However, lots of places are selling all kinds of things with conventional RAM in them, for prices a whole lot lower than infinity. (Unfortunately, hot air is not included.)
The reality of the matter is, the more you scale and stretch, the less you actually design for any given sized platform.

Compare a Galaxy Note to a Droid Razr. They have different sizes, dimensions, pixel densities and various other factors. The UI doesn't just 'stretch' and fix all that. It stretches and looks terrible, feels too large or too small on some devices, and makes fonts et al a mess.

Then throw in a Galaxy Tab, a Kindle, and a more tablet/phone 'tweeners'. Its a total mess. Then throw in operating system versioning and various hardware support and you see why many developers build for iOS first, then consider an Android app.

Edit: I support roughly 200 apps multiplied across all platforms on 20+ app stores. (Roughly 1000 app builds). I see more problems that your average developer sees.
Yes, that is the price. That's the price for native access to the entire codebase of the underlying editor.

So long as it's close enough, you don't need perfect compliance.
I think this is a good idea but the more popular you get the more filtering you need. If 1000 hire-ees want to meet for coffee how will the hirer filter them?

Well I guess I like the idea from the hire-ee perspective. But isn't it a bad deal for the hirer? How does he know I'm even worth talking to? The most valuable asset we have is time and you are asking people running companies to give a lot of it away.
Many of these exotic/novelty interview processes are completely disrespectful of the candidates' time as well. In the past few months I've undertaken a few pretty "rigorous" application processes. A couple of Bay Area startups (I don't live in the Bay Area), and a bunch of other companies both locally and for remote working possibilities.

Startups seem to be the worst when it comes to turning the hiring process into a huge time sink for the candidate. At its worst was one of the Bay Area startups. They outline a 7- or 8-phase interview process. There are independent programming exercises, pair programming over Skype, phone interviews, then at the end they have the candidate in for "cultural fit evaluation" which turned into a six-hour interview gauntlet after flying across the country that morning.

Another bit of inconsideration of my time and my actual job where I work to make money was a company that wanted me to come in in the middle of the afternoon on a workday for 2 hours to "meet the team". I told them I did not feel comfortable leaving the office at 1:30 and go AWOL/take a half day of vacation so I could interview at another place. I wound up backing out of the interview process because of their unwillingness to pick another meeting time, even over lunch.

Then finally tomorrow I am meeting with a company, and they told me yesterday afternoon that they'd like me to prepare a presentation on something I'm passionate about (they liked Jeff Atwood's blog post[1] I guess). This actually I don't mind at all, and think it's a great idea... but I need more than a couple of days' notice. I work 8-10 hours a day, commute a couple more, and by the time I get home I've got 3 hours to spend with my kid, relax, eat dinner, etc. In that 3 hours I also need to prepare a talk on a topic I'm passionate about.

To me that last one is emblematic of these interview processes: good ideas, but not structured with much consideration toward respecting the time of the candidate. I get that hiring the right person is crucial for small teams, no doubt, but I'm getting tired enough of jumping through hoops that I'm not really interested in doing it anymore, even for a great job where I know I can make an awesome contribution.

1 http://www.codinghorror.com/blog/2012/03/how-to-hire-a-progr...
You don't write them in C. You write them in a not-yet-existing language that allows low-level, but safe, access. (Prototypes of this language certainly already exist, I'm not convinced any are ready for this level of prime time.) You probably also have some additional hardware support not yet existing. And while, yes, deep at the heart of the system there will be something or some set of somethings that, if screwed up, could do something like memory corruption, it will be made as small as possible, verified as rigorously as possible, and get the tar beaten out of it until it's as safe as humanly possible.

This will not be a security paradise, because there's plenty of other ways to screw up. Even if we magick a perfect capabilities-based system into existence in 2040, with every desirable property that is promised fully manifested, programmers will still fail to correctly use it, because security is profoundly a Hard Problem. But the same freaking buffer exploit for the ten millionth time should be a thing of the past. (Library support should also be well on its way to making cross-site scripting a thing of the past, too.)
> My girlfriend is in the medical profession.

Ask your girlfriend about her rotations (where students literally cry after being screamed at while working insane hours), MCATs, and how difficult it is to get into any medical school. Job interviews don't have to be as difficult as credentials are both required (there are folks at Google and Facebook without CS degrees -- and that's a good thing, obviously) and are difficult to get irrespective of where you go to school (CS programs wary widely, as this is still a young discipline unlike biology).

Pharmacy is also similar, with a few caveats: pay is somewhat below what a software engineer can expect mid-career (~$120,000 for retail pharmacy, somewhat less for pharma research), residency is not required, but rotations are still insane, and schools are still selective.

In some ways, I think it would benefit the patients if the medical profession was somewhat more meritocratic and less focused on pushing students to their breaking point during rotations and residency, which continues because "that's the way it has always been done". It still somewhat scares me just _what_ a sleep-deprived student could do to a patient due to the very basics of sleep deprivation.

[Full disclosure: I work at Facebook and have dated a pharm student/pharmacist.]

Of course "in the medical profession" doesn't equal "doctor or pharmacist". Likewise, "software engineer" doesn't equal "software engineer at Google or Facebook": there are plenty of firms that don't use coding interviews. Nobody says that to be a software engineer, you have to work at a licensed firm that has to (as part of licensing) use a certain hiring process, require certain credentials, etc...

(This also isn't an endorsement of all modern interview practices: it's particularly silly for startups to cargo-cult interview questions they've overheard at other companies without measuring their effectiveness and calibrating candidates' response.)
Turns on Mythbusters

Narrarator: On this episode of Mythbusters...

Adam shouts: I can't believe it works!

cut to build team blowing up unrelated object

Turns TV off

Well, that answers that question.
I agree with you on all these things, but subject to qualification. I think we need to be developing human spaceflight in parallel with robotic exploration, for the same reason that we don't do all our exploration on earth with telescopes. Air travel is orders of magnitude more difficult than sea travel, which is orders of magnitude more difficult than wandering about on land. I think there is no substitute for getting out there and attempting a wide variety of technological workarounds, notwithstanding the fact that many of these will be futile or fatal. The key plus for me of private or even semi-private space exploration is that failure or fatality won't mean a loss of political capital, compared to publicly-owned and managed space endeavors. Bluntly, we're more likely to discover better technologies if people are allowed to blow themselves up in the pursuit of same. On the last point, planetary colonization is one (remote) endpoint, if we can bootstrap it, but I think asteroid mining and the like also offers the potential of non-planetary habitation, which I find far more interesting. I remain optimistic about the possibility of other propulsive or spatial traversal methods, notwithstanding the limitations from our current theories of physics, though this is a statement about faith in technological progress rather than a specific hypothesis.
I think there's a cargo cult mentality around hiring process. Hiring the right person is hard, and hiring the wrong person can be devastating, so everyone's looking for a magic elixir.
Good stuff, and I'm currently looking. Was hoping for more than a sign-up.
I offered to work in exchange for a local dev consultancy (pybrew.com) in exchange for instruction. I had a basic understanding of procedural code (could figure out for loops and generally make things happen with very spaghetti-ish code) but didn't know what an object was.

At the time, I didn't really know how to solve code problems, how to effectively use docs, or how to use a debugger -- which they taught me. A lot of times they let me build the wrong thing then show me how I could do it better (doing research, learning how cookies work, and reinventing the wheel with web authentication, for example).

'Twas an odd, makeshift apprenticeship program, but it was perfect for me. At the time I didn't realize how lucky I was (I don't think they did either), but I am very grateful to have stumbled upon the opportunity.
> If the pilots on that plane had done nothing like like you suggested the AF447 pilots should have done, what do you think would have happened then?

The plane would have kept flying. Perhaps it would have flown out of the storm, perhaps it would have descended. Either way at some point it would have gotten low enough or warm/dry enough that the ice in the pitot tube would have melted (also the heater in the tube was on, but didn't have enough time to melt it), and the system would go back to normal and all would have been well.

Instead they did pretty much the only thing that could doom it: They ascended. This despite knowing they were near the "coffin corner" - i.e. the highest safe altitude for the Jet. The pilot clearly panicked and didn't want to crash into the ocean, so he went up, and it was exactly the wrong thing to do.

Your point about pilot inexperience in manual flying, is close. But from what I read it was actually that the pilot was used to the computer taking over and not letting him fly in a dangerous manner, this caused him to try ascend to the point of stalling the plane because he believed the computer would stop him.

So you end up with the worst of both worlds: A human who relies on the computer, taking over in a situation with no computer. You have to pick: Either computer all the time, or no computer. Perhaps computer assistance, but no control? Certainly computer override is no good (i.e. this lets you max out the controls and the computer will adjust them to the ideal levels).

> you need situationally aware human pilots.

This was impossible for both of them. The windscreen was completely blank, and (some of) the instruments were disabled. Neither the pilot nor the human had any idea what their situation was. What they should have done was remember where they were and assume they were more of less in the same situation.
I've always liked Heroku's status page. I got to work on a service for apps that provided this type of functionality, but quickly found out that someone here on HN had already tried to have a go at it (it's now down http://news.ycombinator.com/item?id=2110917).

Is there any interest among app developers for a well designed, hosted status site for something like $5 a month?
At some point there will be another layer to YC from successful exits in previous batches.

Already the number of partners is growing, and as more YC companies exit successfully you will probably see more of that, remembering your roots and who helped you up would be a powerful motivator into completing the cycle.

If YC can somehow manage to maintain communications through for instance multiple tiers with bypasses if needed it could get very big.

Every brushfire starts with a spark!
Ask HN: Business Models/Monitization/Gamification
I am looking for the best links, blog posts, talks, videos etc on the following subjects:

Business Models:
Monitization Models:
Gamification Models:

TIA
Hellman's genius mayo marketing software idea
Employers are risk averse with their hiring and so, in the absence of compelling evidence, they will choose to not hire a candidate. Pasting in an answer from somewhere else turns the question (and possibly the whole interview) into a no-op waste of everybody's time. It just doesn't provide the interviewer with good data to make a decision.

My word of advice to you is this: study harder next time, be honest when they hit a gap in your knowledge (maybe they will offer to fill in that gap!), and don't Google on the phone. Interviews are like tests at school - closed book, unless stated otherwise.
> As a build bot? What are you building?

My library upb (https://github.com/haberman/upb/wiki). It is ~5k LoC and builds in 10 seconds on x86. 4gig of RAM is entirely unnecessary. It pays to be small. :)
Google commemorates Robert Moog's birthday with a playable synthesizer Doodle
Have you noticed anything peculiar about the best founders (and their companies)?

Perhaps something they seem to have or do?
This type of setup makes total sense when you work for an enterprise company that spends way too much money on it's own inefficient IT department to use something as awesome as Heroku. You can run this and have your own internal app server that has the git push simple deployment.
In middle school I took a computer science class because it had "science" in the name. Computers were still very expensive and I had practically never used a computer till that moment. One of the modules of the class was a walk through software engineering using the old waterfall model. We had to design, build and test a basic application in Pascal. Nice memories. From there onwards it was all self study.
Could you run a server on this? Something like NodeJS with low casual traffic? Would that work on Android at all?
There's a lot of spread, as in all things. I did the Ivy League thing many (yikes, many!) years ago, and met plenty of genius types and a handful of dunces. And in programming, the divide between people who can learn the subject well enough to pass the course and those who can Get Things Done is very pronounced even at top schools.
On Value and Money
So long as we don't blow said planet up, which so far we have come disturbingly close to doing several dozen times.
VCs as Patrons of the Arts
I wish the engineers at NASA spaceflight, instead of taking a dump on the guy, would applaud his enthusiasm and then explain the better and cooler things that could be achieved with a trillion dollars over 20 years. Technologically they're dead right, but they come off as a bunch of unimaginative jerks.
> Partially because its tone didn't feel like a Star Trek intro

I felt something quite the opposite; I think that Enterprise intro actually best captured the spirit of whole Star Trek - the dream of exploration, advancement and excellence.

Fair point about the Russians though; they deserve more credit that they usually get nowdays.
It's only a matter of time now until we'll have the YC mafia ;)
"Apple are very good at making premium products, they have a greater than 94% market share for computers over $1,000USD"

Wait, what? Do you have a source for that? I'm pretty sure these numbers are not correct.
Thanks for the reply -- the valuation method I mentioned was obviously too crude, so I was hoping someone would call me out on it. I don't know much about finance but I'm actively trying to teach myself. Anyway, it would be good to find a more reliable way to quantify a company's long-term, potentially risky growth opportunities.

This calculator: http://www.ft.com/cms/s/2/8a21debe-944e-11e1-bb47-00144feab4... was kinda useful, but a more detailed model would be interesting.
I've been asked bit twiddling in O(log n) questions before and it was in no way supposed to be a test of my knowledge. It was a way for the interviewer to evaluate my ability to not know how to answer a question. It took me almost an hour to solve, but it gave the interviewer a pretty clear insight into my ability to approach something new.

In my experience the best interview questions I've had have been situations where I was asked a question about something I was not familiar with. The interviewer then gave me a 5 minute overview of the things I need to know (like which synchronization methods are available in pthreads, for instance) and then give me the chance to apply the things I just learned. I think most employers care far more about how quickly you can pick up new things than they care about what you already know, and it left me with the feeling that they gave me an offer because of what I can do, rather than what I already know.
USF researchers question safety
Here's The Inside Story Of What Happened On The Facebook IPO
Ah, touché they have too. I forgot about their foray into both geo-thermal and solar power.
"I don't care about their IQ, education, etc."

Would you say that is true of the other investors as well?

Are investors informed of the IQ, education, etc. of the each member in the group?
The site is being served over ipv6, they are just redirecting you because your Host header doesn't match what they want.

This works just fine:
curl -g -H "Host:www.facebook.com" -H "User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.46 Safari/536.5" "http://[2a03:2880:10:1f02:face:b00c::25]
I know mobile is hot right now, but does this really have to be an iPhone app?
Agreed. We're working on a ranking and reputation algorithm that will only show the best Coders for the Startups. We don't want to waste anyone's time, on both sides.
Cool visualization of the Marianas Trench
L4 was verified to the tune of about $4.6 million dollars, or $500 per line of code. And that's for a microkernel under 10 KLOC. And that's assuming no changes are made. Ever.
It's amusing to think that someone may be subverting my silly interview questions. If you were being cleverer than the interviewer, I suppose that's a fair way to succeed.
Software "Artificer"?

Artifice: "Clever or cunning devices or expedients, esp. as used to trick or deceive others: 'artifice and outright fakery'."

Not necessarily the greatest way to describe yourself...
I got several paragraphs in and thought, where exactly is the Ruby?

Further to that, having inline code (without any monospace formatting), and talking about binary trees as an intro to Haskell, well, I would suspect that it alienates the people it tries to introduce.

I'll own up to my ignorance, of course. I've no CS degree, I've encountered no occasion where I'd implement CS classics like linked lists and binary trees. My understanding goes as far as sort of vaguely recognising them. I'm not going to boast, but I don't doubt I'm alone here.

I couldn't finish the article, because the content didn't match the expectations the title set.
The same could be said for climbing mountains or racing cars at high speeds. The point isn't just to gain knowledge though, the point is to go, to do, to live.
no. not a bubble.
What kind of business strategies would be compatible with that?
Ask HN: Confronted ethical dilemmas while developing a health community
Have you worked in or for a company that developes web-based health communities and confronted ethical dilemma there? I mean, health communities like patientslike.com offer great opportunities for programmers, database designers and owners of the company (user submitted data can be sold), but health as a concept isn't very strictly defined -- how could it be?

It is quite easy to take some condition (one database table: "condition"), associate some drugs to it (another db-table) and let users tell that they have certain condition and that they have tried this and that drug for the it (few more db-tables). Ofcourse it would be nice, if users could somehow tell that they have some (preprogrammed) symptoms like "brain fog" (another db-table). Add something more that users can select and soon there will be enough information for automatically generated stats.

For example: http://www.patientslikeme.com/symptoms/show/189
(I'm not implying anything the referred site. I'm just using it as an example.)

Researchers and drug manufactures might find the stats useful in some way (by seeing some kind of patterns that other maybe can't) and the others could atleast satisfy their curiosity related to questions like "what are the top 5 in..".

However, from the user's point of view (potential or actual condition/symptom carrier) certain issue might arise: he thinks that he has found "soulmates" (in larger health communities "with blogs and everything"), but even when their symptoms match, they might have nothing in common at the neural level, for example. Actually, both of their conditions could be caused by different enviromental issues, but user couldn't let the System know, what kind of environmental issues might be involved -- and that's why the user keeps trying different kind of medications that other "soulmates" have tried (might take 10 years to go through all of them).

Think about Asperger's (aspies, like they might say). They seem to have something in common, but that might because the definition of the symptoms and their naming is too vague. Same goes for the criteria of many conditions. That would understandable in some sense as we as humans prefer to use common words like "socially handicapped" (instead of something more cryptic).

At this point you should be able to see what I might mean. This question was targeted to those, who has been involved in companies developing web-based health communities, but others too might have an opinion or two.