I've been experimenting with extending OOP to potentially implement functionality that could make a particular AGI design easier to build.
The problem with SE is that it brings along much baggage that can totally obscure AGI thinking. Many AGI people and AI people are automatic top of the line software engineers. So the type of SE for AGI is different than typical SE and the challenges are different. I think though that proto-AGI's will emerge from hybrid SE AGI organizations either independent or embedded within larger orgs. Though some AGI principles are so tantalizing close to a potential software implementation you can almost taste it... though these typically turn out to be mirages... John From: Valentina Poletti [mailto:[email protected]] Sent: Saturday, December 20, 2008 6:29 PM To: [email protected] Subject: [agi] Relevance of SE in AGI I have a question for you AGIers.. from your experience as well as from your background, how relevant do you think software engineering is in developing AI software and, in particular AGI software? Just wondering.. does software verification as well as correctness proving serve any use in this field? Or is this something used just for Nasa and critical applications? Valentina _____ agi | <https://www.listbox.com/member/archive/303/=now> Archives <https://www.listbox.com/member/archive/rss/303/> | <https://www.listbox.com/member/?&; > Modify Your Subscription <http://www.listbox.com> ------------------------------------------- agi Archives: https://www.listbox.com/member/archive/303/=now RSS Feed: https://www.listbox.com/member/archive/rss/303/ Modify Your Subscription: https://www.listbox.com/member/?member_id=8660244&id_secret=123753653-47f84b Powered by Listbox: http://www.listbox.com
