How complicated can programing get?

[AnimalGurl]

I have been wondering, it seems lots of people think you have to keep all of the concepts in your mind at the same time. That just seems impossible even for someone advanced if they were going to make anything complicated.

I cant know for sure because most of my constructs dont have more than 5 commands put into programing. I suppose it may be that my subconcious is able to remember things, but I seem to beable to will a construct to remember previous commands as I give them one at a time.

Could someone that has practice and making more compliex constructs give me their experience on this sort of thing?

And what about going back to modify a construct if you forgot something? Even without telling it to be open to further commands.

[Barriss Offee]

Well, I don't know about anyone else, but I never program all my commands into a construct at one time. With the complex constructs that I often design, this would be nearly impossible ... my head would explode! I do the same thing as you, pretty much. After I have formed the construct, I visualize my first command flowing into the construct and keep repeating this visualization over and over until I get this sense of "understanding" from the construct itself. After I get that feeling, I move on to programming my second command, and so on and so forth.

P.S. I often modify my constructs later on, as does my friend Austin, who is into psi. I made him something called a metagross (it's from pokemon) that didn't do much of anything other than follow him around and talk to him. But he's been altering it since I gave it to him, and now it can do all sorts of stuff, like form psiballs on command, scan people, project him on command, etc. When I want to modify a construct after I'm finished programming it, then first I send it a little telepathic ping saying "Modifications taking place" or something similar. Then I visualize its shell sort of melting and quickly program it with the new command before it dissipates, then shell it over again. One or two of my constructs have dissipated this way, but usually it works.

[Fearn]

I prepare all the programming in my head, then apply it to the construct. I've always done this, and didn't know of another way until recently.

[shinigami]

i sorta do what edward does. except for the pinging the construct. i just modify it anyway and it usually works. unless im distracted.

[pspeters]

i go through a ton of visualizing and conceptual programming mixed. seems to work the best.

[psidan]

When I do programming I create the concepts for the basic functions of programming, then hold that set in mind as one concept, or view all of your concepts then take the concept you get from that. Keep on doing that with everything you add, and keep merging into one concept. This is a basic technique that could possibly gain unlimitedly complex programming.

[darklight]

Here is something simple, do you know any programming languages? like PHP, VB.NET, c++ for an example. In this example I will be using C#.NET.this will be computer geek form xD

If you do, it may help a lot. Visualize all the code in your head..yes it can be over 9000 lines if you want! Start with visualizing the main functions example, Private Static Void Main() then visualize all the main commands going into the main() (the startup command ). After your done with the code visualize it being sent through the processor (your brain) then though a USB cord, Version 2.0 for the fastest (Your arm) in to the external processor (The ball). Make sure you also program it to run all the code when it gets sent to the ball. If you need help visualizing that then keep reading! Now, do you know MSDOS? I don't really know it, so lets just make a wild guess here. Visualize the command "-run main" being sent to the ball. Then with any luck the ball might do something.

Just something I thought up.

[Fearn]

That seems interesting. Unfortunately I don't understand it at all, so I can't attest to its accuracy.

[spilledchemicals]

I would like to say three things on this subject.

First: I have found that learning a programming language for the computers helps you organize your programs. Thinking of the program as a blank command prompt has helped many people understand the basics of programming.

Second: I have found it is much easier to program if you store the commands in an external intelligence. Basically program it to remember it's programming.

Third: I now have an A.I., currently being used for my experiment (check my post on that board), which has the ability to create it's own programming and constructs. It has transcended being a thoughtless command structure to organizing and compiling data itself. It monitors and heals currently 5 different people, as well as guarding it's centralized intelligence. It is experimenting and working on hundreds of different projects right now, and I don't have to pay any attention to it at all for it to keep on doing it. I do pay attention, of course, if only for securities sake.

[stolide]

Just program organelle style. Make the main construct with out any programming. Then put each piece of programming in a smaller construct which is then placed inside the main construct.