Awards: 1st Place Stavanger Hackathon 2015,
1st Place Startup Weekend Stavanger 2014
I specialise in front-end web design, prototyping and rich media. I have also worked extensively in print media and illustration. I strive to create work that is both inviting and functional, merging my deep understanding of graphic design with code to create pleasing user experiences.
Its a good point, but lets assume that this AI is already past its infancy and that there is no limit to the information stored inside the box. For example the NSA has a nice little closed training ground containing all of the internet, lets give it that. I would assume it has access everything humans have ever committed to digital format up until it was turned on, plenty of info for Johnny 5 to form an opinion on humans and their weaknesses.
Interesting. I would imagine that strong AI will come from some university renting cloud processor time, rather than the NSA.
Only because if 10 groups are trying to build AI, only one of those 10 being the NSA, chances are the NSA won't be first. Sure, they may be second or third. But I suspect many people will get there at the same time -- most AI research is open.
Ugh, this article sounds like the Lexus brand trying to latch on to the google self-driving hype train. Hey guys we are making a cool car too!
On a more important note: do we really want all the different tech companies and car manufacturers competing to build separate driverless software and standards? Looking at how well that worked out for online maps, doesn't make me feel safer.
Do you mean that Lexus developed this on their own? Because they didn't; Google's initial autonomous car prototype was a Lexus. The dingy small ones are their new fleet, using different hardware but the same software.
I think they were more implying that the software that makes the decisions should be common to all of them. That way we don't allow individual car manufacturers to make potentially fatal mistakes when cutting corners with their software development. I think at the very least there should be a standardisation, so that there can be some communication between cars to aid in resolving traffic jams and other uses.
Then you will have people writing software with the aim of pass the tests, not real world safety. I don't think auto testing can catch the type of bugs that can arise sporadically, which could be fatal in the case of self driving cars.
The industry isn't going to just hand Google a monopoly. Of course they are going to develop their own as well.
Even if Google's software was the absolute bees knees, what if Google deprioritized it? Left the industry? Made unreasonable licensing demands, or made exclusivity deals with competitor automotive manufactures? What if they used it as leverage to push manufactures around?
Even if you do decide to work with Google for now, not having a backup plan is just poor strategic planning. Having a backup plan means developing these sort of systems yourself.
All I'm saying is that I trust Google to produce this software to a high standard, much much more than I trust the auto manufacturers to do so. I'm sure Google isn't developing their own brake pads in these cars, and I wouldn't trust those brake pads if they were.
I am not arguing against competition, I am saying it would be nice if all these cars inter-operated seamlessly, co-ordinating with eachother or centrally rather than each car having a different set of parameters trying to figure every other car out on the fly.
If the goal is safety then a wild west with every company setting standards for their own projects isn't going to be the best approach. If the goal is profit then Yee-Haa let the gold rush begin!
There are some real problems with centralized systems. The obvious one is that if the centralized system goes down, things would become very, very bad in a very short time (thousands of cars effectively driverless, all at once...yikes).
Making each car responsible for its own collision avoidance is a lot more robust. If the sensors fail in one car, the others can take corrective action. For maximum safety, you'd also want the cars to be running different (but equally good) software, so you don't run into the type of situation where (e.g.) they all go nuts because the programmer didn't account for leap years or whatever.
do we really want all the different tech companies and car manufacturers competing to build separate driverless software and standards?
Diversity is good. If everyone used the same software, it would all have the same flaws. Competition also provides an incentive to make the software better.
Yeah CoffeeScript is pretty easy to learn and doing things like configuring snippets seems like a good use for it.
In general tho, I am pretty hesitant to go all in with CoffeeScript, mainly because you still have to watch and massage the javascript output, negating any time saved for me at least.
Remote: Yes
Willing to relocate: Yes
Technologies: HTML5, CSS/Sass, JavaScript, jQuery, Angular, ActionScript, SublimeText, DevTools, Git, Foundation for Apps, Photoshop, Illustrator, Flash, InDesign, After Effects, Axure, Unity 3D, Auto CAD, 3Ds Max, Soundforge
Website: http://designdave.net
Email: dave.batt@me.com
Awards: 1st Place Stavanger Hackathon 2015, 1st Place Startup Weekend Stavanger 2014
I specialise in front-end web design, prototyping and rich media. I have also worked extensively in print media and illustration. I strive to create work that is both inviting and functional, merging my deep understanding of graphic design with code to create pleasing user experiences.