Skip to main content

Google technician to focus on voice commands | Latest Industry News | News | Opinion, News, Analysis | BCS - The Chartered Institute for IT

07/10/2011

One of Google UK's best-known programmers is to relocate to the company's Mountain View headquarters to help realise the potential of voice-powered search, reports the Guardian.

Dave Burke will make the move to San Francisco as part of the computing giant's push to improve speech recognition technology, after joining the company's UK arm in 2007.

Google's London base has been key to the engineering effort that has gone into Google's Android smartphone platform, the world's best selling mobile operating system.

Although Android phones do accept voice commands for searching, email composition and summoning maps; because accuracy is still low, developers are racing to create technology that will eventually replace touchscreen typing, suggests the Guardian.

A specialist in voice recognition technology, Burke has published a number of academic papers on the subject and had around 80 programmers and engineers reporting to him while in London. Google has said it is 'not able to comment on the internal movements' of its staff.

Apple recently revealed its iPhone 4S, a direct competitor to Google's Android phones.

An actual interesting piece of insider information from the BCS. I am amazed. On the story itself, I hope Google do something to improve their own voice capabilities. One of the biggest problems for me is the need to be connected to the internet though. My voice commands usually just get stuck in some horrible loop consulting the cloud. I think it will be interesting to see how useful Apples Siri system will actually be. I predict it will be poor.

I seem to recall that my Nokia N70 had excellent voice recognition (considering) and so does Windows 7. Neither of these need a constant connection to the net.

Comments

Dom said…
A gutted, it's been pointed out to me that they didn't break the story. http://www.guardian.co.uk/technology/2011/oct/06/google-technician-mobile-voice-commandI don't like sites pilfering stories without a link back to where they got it from. It stinks. Obviously there isn't proof but the BCS story is from today and the Guardians from yesterday.

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second