Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon.

Pages: 1-

There's just too much

Name: Anonymous 2012-06-13 5:41

so many things to learn
not enough time, life running out
the code, a black morass of details mingling infinitely
will i ever understand?

Name: Anonymous 2012-06-13 5:43

Nope.

Name: Anonymous 2012-06-13 14:45

by the time i was 17 i already knew everything

Name: VIPPER 2012-06-13 14:53

Write an AI problem solved.

Speaking of AI, anybody know any good literature or whatever on that?

Name: Anonymous 2012-06-13 16:17

>>4

You are thinking of AGI, which means artificial general intelligence. There will never be a quick way of creating an AGI because the smarter it is, the more concepts it has to handle. Why? Because that's how you define intelligence. Or am I wrong?

AI is just a professional way of saying program to do a certain task or set of tasks. When people talk about teaching an AI, it means they are using a natural way to evolve a program so it reaches a particular fitness for a given task. If the fitness function is designed so that the program evolves (converges) as quickly as possible and the fitness value said function agrees with your definition of fitness for the problem, it is a good AI.

Neural networks or support vector machines are just different structures for the I/O system (feedforward or feedback) and the evolution process to take place. You could as well use something like a cellular automaton, but personally I have found that simply using whatever CPU instructions you have available is the best, fastest and overall nicest way.
What matters is the fitness function. You design the fitness function for the algorithm above, be it neural networks or whatever you want. But the "intelligence" of the program comes only from a good fitness function. You also need some sort of recombination/evolution algorithm, but that is a trivial thing to implement and often you find good ones accidentally, since evolution tends to just "spring up" from nowhere.

Name: VIPPER 2012-06-13 16:28

>>5
Yeah something like that except that i can actually learn what the hell you talk about and why that is so.

Name: Anonymous 2012-06-13 16:33

>>6
I suggest using the Google search to find out about some of the terms I described in bold. Wikipedia is also a good source of external information.
However, the main problem you have is that you depend too much on others for information. People have different opinions and our understanding can change. The best way to learn is to try and experience. Go into it and feel it like a true VIPPER. It's the only way you will understand.

Name: Anonymous 2012-06-13 16:33

>>4
PAIP if you haven't read it already.

Name: VIPPER 2012-06-13 16:45

>>7
Thanks, i just asked because i thought some people here had some more knowledge about these things.

Name: Anonymous 2012-06-13 17:06

>>7
Hax my anus.

Name: Anonymous 2012-06-13 22:06

Don't learn Object-Oriented Programming. It's just wrong in every way. This advice is from a 20 year veteran of the software development field who learned OOA&D, design patterns, and all of that madness. It's just mind rot.

Name: Anonymous 2012-06-13 22:18

>>11
I was going to make a snide remark and the I realized how important 20-year old code is.  That's called "legacy" and oft-times "the crap we don't know how it works anymore because it has a lot of undocumented layers piled on top of it."

Don't change these.
Name: Email:
Entire Thread Thread List