At the end of December 2012 I said that I felt that I had figured out a way to write an AGI program. I then said that if someone really did have it all figured out that he should be able to write the program in a year. I then changed that to two years. For one thing we should give a researcher, even an amateur researcher - especially an amateur researcher - some leeway. And for another, it should be clear that writing an AGI program that could actually work must be pretty difficult. I also added that other contingencies, like health, could intervene on the schedule. But I then pointed out that there are some indicators that should make it clear that the programmer really did not have it all figured out. Like if he worked on it for 5 months and still had not started in on experimenting with some actual AGI situations then that would be an indicator that he wasn't working at as advanced a level as he might think. Expanding that to twice that length is 10 months and I am there. However, I did have a worrisome health problem that really did cost me about a month's time of work. So this means that if I am not working on the AGI experiments within the next month, after 11 months have passed, then I believe that will be a strong indicator that I really did not have it all figured out - as I felt that I had last December.
One of the hang-ups that I got into was that I wanted to write my own data management system. It has been an interesting project but I probably should have used a simple data management system in a very direct way so that I could get to work on the AGI prototype. If I actually got the prototype to a promising stage I could then have worked on the data management system. That is a reasonable point of view. However, there is an alternative view. A conceptual management system, in my opinion, is going to be complicated. If I can't write a simple foundational data management system then I probably would not be able to manage a conceptual management system. So from this alternative point of view, all the time I have been spending on trying to write my own very basic data management system may turn out to have been a reasonable investment, given my goal. I just started thinking about a problem that I would have if I shared my program. My program is converting the various arrays it has into byte arrays to save them to disk using a fundamental strategy that I found in the .net help files. However, that means that most of the data will be saved according to the Little-Endian implementation of my computer and I just started wondering how I would make the files available to other kinds of implementations. I guess I could write a simple conditional algorithm for the file accesses so it doesn't seem like it would be a big deal. But even worse than that, the files would be such a security risk I am not even sure that they should be casually shared. So how should I deal with this problem? I'm not going to worry about it now. This is exactly the sort of thing that I shouldn't be worrying about because I should be more focused on developing a prototype. If the prototype actually worked then I probably will be able to find a way to deal with these side issues. Or at least the Little-Big-Endian problem looks simple. But the shared file security problem is not that important to me right now because I have to try to avoid the pitfalls of additional complications. I have to focus on getting the project to the next stage and just see what happens then. Jim Bromer ------------------------------------------- AGI Archives: https://www.listbox.com/member/archive/303/=now RSS Feed: https://www.listbox.com/member/archive/rss/303/21088071-f452e424 Modify Your Subscription: https://www.listbox.com/member/?member_id=21088071&id_secret=21088071-58d57657 Powered by Listbox: http://www.listbox.com
