IT

As human reality slows the machine being operated speeds up because the operator tells the machine to do something and this could be a 1:1 relationship like operator input to machine output. However if the machine made a million steps then we can see how a 1:10^6 ratio (this ratio measures one step of the operator at the panel vs. a million steps in the electronic circuits of the machine and the outcome of those steps, therefore.) would speed up the machine up to light speed and slow perception for the observer at the max and when we as operators speed up the machine slows because it has to wait for its operator. So then here perception speeds up for the observer, the personal operator. Is this Einstein Roger? I think so. How? Relativity. General Theory, Special Theory, [[apply it

When I speed up then reality slows, but when reality speeds up then I go slow. Well this is just human perception and we really no that there is no causal grounding to this but not the case in psychic behavior. I don’t know yet but it seems as though its only my perception of the world and everything around me. When I work slow then the world seems fast, when I work fast and get a lot of things done in one day then everyone else seems slow and I have more time for leisure. When I drive slow other cars pass me by when I drive fast I see everyone in my rear view mirror.

slowUser fasterMachine

—————— = ——————- = 1 = True inversely pro???

fasterMachine slowUser

When working on your computer, and in my case Windows, if you accidentally discover a fix then quickly create a theory as to why the computer just did that. What were the steps just taken in order for that solution that you just discovered but not previously known?

Now if the steps are still too numerous for memorization, don’t write them down but at least try to remember the essence of the entire thinking process in your approach to the fix. Then come up with a hypothesis that goes something like, “ok, if the computer does this then do this and it will bring me to a working solution at the least.” And then test out your theory by carrying out the same step(s), see if you get the same or the desired solution to the same or better degree.

Granted the problem the first time around is unique and therefore your first instinct is to write it down, but then you are going to get pages and pages of a solutions manual that you might have to carry around on your person or depend on the cloud.

When entering a problem on the computer before fixing it tell yourself ok “I’m going to understand what the computer is doing in the next steps that I take and see if I can come up with a fix.” Believe in each step that you take towards the solution. When you start to believe in each step and it makes sense or that it is an accurate step then you start to align yourself with the machine. And when this happens time after time and there it is where you start becoming proficient. But all this doesn’t really, but not entirely true, unless you come to a final step in the fix where the outcome is desirable. There is always a solution because the computer never errs; it is just doing what it is built to do by us. And since it is built by us , it is a reflection of our thinking and granted there have been countless hours of labor by geniuses that went into building such machines, but yet still and no doubt they have to be user friendly or these machines would exclusively be in the hands of the few. The elite. And they are not!

Believe in the steps and understand why the piece of that software needs to be fixed in such a manner in order for the desired outcome to function properly. Thus you make the fix work. This could be the Operating System or any other software used by you. I’m trying to mesh Information Technology Engineering here with the Scientific Method as a form of art.

When you find a solution then that is exactly one solution that you know that works for sure. But it’s sort of like mathematics: sometimes there is one solution and one straight path to it or you can have different paths in tweaking and get the same effect. And there can be multiple solutions.

What I want to say is that if you stay in practice as an IT Engineer and fix problem after problem you need to bring your thinking in alignment with the kind of software you are using. For example, I have to believe what Windows is doing and all affiliated software by Microsoft in order to fix Windows machines.

Your thinking becomes like a Windows machine. Your mind becomes organized like a computer; and life becomes easier. Soon you’ll find ways to maintain the computer so it rarely breaks down. It takes a lot effort but it is worth every try. It is my belief that working in this manner improves the logical construct in your thinking processes and makes you smarter. What I want to say is that you want to feel the machine and like it for what it is. This happens because computers are based on logic and programmed to rules that only we can instill in these machines. Therefore the more you interact with them, the better your train of thought becomes over time.

And the more of the complexities of understanding these machines of which really can be attained by an individual will only further not only there use in production but to further the technology in ways that never before imagined possible.

[[[windows fixes are consistent from operating system to operating system. You can fix it by taking paths in clicking objects like in Windows 10 Pro and do it the old fashioned way and it works. If it happens again before 3 days and you still remember how to fix it create a macro like alt + {x} and apply the fix in two strokes. <—–{{{ I got a device driver error on my VEATOOL wireless headset so I opened up control panel to bluetooh icon in device driver applet ; disabled the driver then enabled it. Then it worked. I don’t know why you have to do this occasionally to get your headphones to work. But then again this is the only operating system I am familiar with. See ya.