Home // Blog // Planning and Programming

I’m going to depart from convention a little here and start by teaching programming before energetics.  I believe that programming is by far the more important skill, especially in the method of construct-creation described here.  Energy manipulation is relatively easy, but of little use if you can’t programme the energy you’ve gathered.  Contrary to what some may think, you can learn to programme before you learn to manipulate energy, which will leave you better prepared to make good use of the energy you’ve gathered.

The trick when programming a construct using this method is to gather all of the construct’s attributes into a single, cohesive whole prior to creation.  I find it messy to gather energy, then make the construct bit by bit, adding attributes (duration of life, abilities, etc), then giving it its tasks, then adding more and more info one piece at a time.  It’s less complicated to spend a little time planning first, and then execute everything as a single step, rather than adding a half-dozen afterthoughts as you go.  You can certainly add the afterthoughts later, if you so desire, and we’ll cover that a little later.
As an example, I’ll run through the planning of a simple construct, whose purpose it is to manipulate traffic lights.  We start with what it will do, which is to make lights turn green as you approach, or at least to speed up the transition from red to green.  Is there anything else it should do?  What if the light is already green?  In that case, it should cause it to remain green until after you’ve passed it.  How about things the construct should not do?  I’m not sure there are any really dangerous ways of doing the above, but to be on the safe side, let’s add that it must do so without harming anybody.  It might cause a bit of consternation to other drivers, whose turn waiting at the intersection has been extended, but that’s to be expected.  Stick with the basic idea of not causing anybody any physical harm and you should be fine.

We now reach the all-important “how”.  If you make your construct go about its task in a specific fashion, you are limiting its options.  That works if you know precisely how you want something to be done, but in this case I’ve frankly no idea how traffic lights work.  If you approach the problem with the attitude that your construct will be able to do it, then it will find the most expedient way of getting it done itself.  Within reason, of course.  A little experience will soon let you know what is and is not possible when working with constructs.  You should add, however, that the construct must not hinder or delay you in any way.

Next, come up with a name.  Lots of people skip this step, or at least they avoid adding a really creative name.  If only for the purposes of reference, you’ll likely end up calling your construct “the traffic manip construct” or something similar.  Just to illustrate the point, we’ll name this one Traffic Light Construct.  Next it’s good to give it a form.  It is perfectly acceptable to stick with the orb-shaped psi-ball configuration that’s become famous in psionic circles, but you shouldn’t feel restricted to that form simply because you’re new to this.  Selecting a form that follows its function is a way of mentally reinforcing that function (Bauhaus psionics!).  How about a floating green light?  If another form takes your fancy, say a little flying traffic cop, a green traffic light fairy, or something equally fitting, then feel free to use it.  What is important is that you make sure the form is firmly associated with the idea of the construct named Traffic Light Construct.

The point here is to get all of the different things together as a single idea.  To give you an idea of what I mean, let’s take a look at the humble alarm clock.  Just thinking the words “alarm clock” will bring up the concept of an object with a fairly predictable form, with the following attributes:

  • Displays the time
  • Emits a sound at a pre-arranged time
  • Stops the sound at the push of a button

If you wanted to create a construct alarm clock, you’d have the “schematics” already in your mind.  Because we’re working with thought alone, all you need is to have what you want clearly defined in your mind beforehand.  All of the concepts come together to form a sort of package of thought.  From there, you simply externalise that package in an energetic form.  Let’s return to our Traffic Light Construct.

Don’t forget to specify how long your construct will exist.  Setting an expiry date is a good way of ensuring a construct won’t hang around after you no longer have a use for it.  You can specify that its life will end after its task is complete, but it’s a good idea to also give a time limit in case it fails in its task.  For long-term constructs, such as the one we’re creating now, you might like to give it a life of one year, and recreate the construct after that limit has expired.  Don’t forget to add the date to your calendar, however, or you may suddenly find yourself wondering why the traffic lights are no longer changing.

You must form a package of thought, a series of related ideas that fall under the heading of Traffic Light Construct, and define it as a whole.  Giving it a name helps tie it all together.  Giving it a form also gives us a focus.  The easiest thing to do when starting out is to put this all on paper, or type it into a word processor.  Here’s what you’d write for the Traffic Light Construct:
Name – Traffic Light Construct

Intent – Cause all traffic lights to be green as I approach, and to remain green until I have passed them, without causing anybody physical harm.  Active only when I am driving, or a passenger in a car.
Form – Floating green light

Power – Ambient (We’ll get to this later)

Duration – One year

Once you have it all down, you need to mentally tie it all together.  The idea is to link all the concepts together as a single idea, a single package of thought.  Remember the alarm clock?  That kind of instantaneous recall is what we’re aiming for.  The easiest way of doing this is to run over it in your mind a few times, until the name brings up a mental image of its form, and the intent is clear in your mind.  Obviously this is more difficult to do with more complex constructs.  With practise, you’ll find it gets a lot easier to pack it all in there.

Sounds too easy, doesn’t it?  I’m aware that this is very different to other methods of programming you may have read about.  It’s also the simplest and easiest way of creating the programming from scratch.  Using this method doesn’t prevent you from altering the construct after the fact, and we’ll get to that in a later section.

0 Comments ON " Planning and Programming "
  • alt_example

    Michael June 28, 2014 at 1:53 am - Reply

    I tried this the other night, with the “Attention Getter” construct,and nothing happened. I struggle to visualize certain things, so I tried to just imagine the glowing blue ball, I programmed it and everything but nothing happened. Do you have any suggestions?

  • alt_example

    kwan white July 23, 2014 at 9:01 am - Reply

    i didn’t really understand this article. some points might have been forgotten or skipped

  • alt_example

    Neilesh December 25, 2014 at 8:28 am - Reply

    Nice article. i liked the way to manage constructs by writing them down. but i prefer creating another Master construct for taking care of all other construct. its like hiring a maid… 😉

leave a response