920 karma · joined April 22, 2009
Also: Free speech-to-text app for Mac (dictator.robgough.net) Free tmux agentic wrapper for Mac (belfry.robgough.net) Free screenshot annotator for Mac (shotandtell.robgough.net)
I think going OS is a bold move, and with a bit of luck (and community interest) it should help propel some interesting developments and keep it at the cutting edge in the post-reader landscape... and if that expand all thing annoys me enough, I could just code it up myself.
Thanks!
Have you given any thought to being able to import existing posts that are in markdown format? I'm currently using scriptogr.am and have a number of posts that ideally I'd like to import.
http://newsroom.fb.com/News/604/Messaging-updates-for-iPhone...
I'd expect someone with 3 years web dev experience to be anywhere from mid-20's to mid-30's outside of London, and a cursory search for Suffolk that appears to be about right.
Judging by the amount of people I've spoken too over the last few days, there's a whole lot more than 500,000 of us. I'd love to see how many people Google considers not worth their time. I'd happily pay for Reader.
I like what you're saying about keeping it narrow by the communities you're targetting. If it's truly useful, and generic, then people will start finding their own alternative uses.
I wouldn't have three different type of question on your front-page header;
1. Lost my Dog, if you spot it ... 2. Wanna play a game? 3. What is...
I'd pick one type (personally, the 2nd) and stick to that. 1. is only useful with significant localised usage and 3. is better left to something like twitter for now.
Whatever you do, best of luck.
If you manage to get X number of people to sign up, currently they likelihood of finding someone who wants the same thing is significantly lower than if those X people all signed up to looking for a similar thing.
Though I should imagine there is some advantage to keeping it generic to a point (sport over tennis) as someone may just be after someone to play games with, and might also be up for badminton or basketball or whatever.
The subject turned to technology, which it normally does when I'm around family, and he showed me his "fancy" Nokia that was especially equipped to help him out. It was very expensive, I presume it came to him through an organisation that helps blind people (he did say, but I've forgotten those details), and he showed me it's special assistive features claiming (with humour) the he would be willing to bet mine couldn't do that.
I flipped out my iPhone (4 at the time I think) switched on the assistive settings (which I'd not done before) and handed it over to him. He had it figured out almost instantly. What blew him away was that the price of this fancy new phone brand new was still significantly cheaper than the phones available through his normal channels - and it was his opinion (after an admittedly short time with the phone) that this was more useful and easier to use than his current phone.
Accessibility is something I think is probably (note I said probably, I have no evidence either way) overlooked by most the startups around here - but I think Apple are trailblazing here too. For most of us these are features we may not even know exist, but for those who need them - they really need them. To take them away could literally be life changing.
The iPhone (and really, the iPhone 3G for me) is when prices started to become reasonable.. nowadays, you can get decent data plans with (almost) everyone here.
Perhaps a title change in this case wouldn't be all that bad.
An SSD however, is incredible. I originally wrote "essential", though I guess it's not... but it certainly feels like it is once you have one. The downside is that it will make working with non-SSD desktop machines irritating-as-hell.
Give these guys a break and work with them one on one to find a solution to your problems.
In the article it sounds like instead of them trying to work one-on-one to fix the problems, they just outsourced it to a digital removal firm. If that's the response he got, in what way would you expect the OP to be able to work with them one-on-one?(TFS obviously for Microsoft houses only.)
As it is right now, it's ultimately the trusts themselves (as is my understanding), but what safeguards will there (or could there) be in place to keep this data safe.
And what about that data? Do we force any new staff-written applications to create their own MPI etc. or do we let them access the main systems through some kind of API? In which case, that would need creating - and interfacing to a variety of different software is never simple. If it's all to stay on the internal network, then who hosts these apps - and where does that budget come from?
There are a lot of big questions and potential risks here and I'd be very interested to see what these eye-catching initiatives turn out to be. Until I see evidence to the contrary, I remain pessimistic about these being anything but trivial and largely pointless.
If this was a serious effort, why ask the doctors, nurses and other clinical staff to learn to code - and not reach out to the open-source development community and ask them for their help. I'm sure a great many developers have, or know someone, who has used the NHS and would love to have a part in making things better.
What an achievement. May he rest in peace.