danielgrieve

I created a project using the Ruby sample app, but that's about as far as I got (same Setting up Environment problem that others are reporting).

I thought I'd try deleting the project I created, but it doesn't seem to do anything. It's also very weird to have a checkbox to delete the project, and then clicking "Save".

I've actually had the domain name poole.io sitting for a while now, ready to do something that supports Jekyll. Great minds think alike?

That's true. At the very least a browser extension would be doable in a weekend.

Why didn't they just, you know, talk to each other? It sounds as if they were sat next to one another at the same computer...

You're right, that is definitely an indicator that his code is absolutely horrible. He should have spent more time obsessing over which letter to capitalize.

It isn't web-based but http://www.fuelcollective.com/permute is a nice tool.

I think archenemy meant on the site itself rather than on HN.

The services are trying to provide you with easy access so you don't have that barrier of creating "yet another account". Depending on the service they're offering they'll pick a reasonable third-party that offers oAuth integration.

I'd say that GitHub auth for a service aimed at developers is a reasonable assumption to make.

Don't assume as much, as recent as today: http://www.bbc.co.uk/news/health-20713985

Quite ironic considering there isn't any interaction. Effortless indeed.

I wouldn't exactly say they've failed. Maybe I failed in that I wasn't accurate enough with my search terms, but I've found the results I was looking for on other pages countless times.

Though it would be interesting to find out how many people do only check the first page before retrying their search.

Another positive for open source I'd say!

I have to agree with pretty much all of your points.

Securing Patient Identifiable Data should be near (if not at) the top of the list of priorities. Some API where data can be requested which only returns non-PID data would probably be the way forward, but there will certainly be cases where there is a need for certain data that will be identifiable.

I'd probably say that NHS staff don't need to learn how to code, but should instead work much closer with those who can.

As in an "insider" there is an endless list of services that could be improved with software if we could just open our doors slightly.

As a web developer within the NHS (though in Scotland) I can already tell you that the problem won't be that NHS staff can't code, but will be that they won't be allowed to code.

The main issue is always the archaic IT department who lock down computers, rendering them near useless. That would be the first place to start. Then we can start teaching our staff to do something other than create a Word document and visit their staff Intranet.

But it isn't by the backspace... in fact it's almost the furthest from it! Probably depends on your keyboard layout though.