index

Secretarial Program

Page-2: Errors, Alarms, Notices

Errors:

This guy represents something INSIDE my program. Our bodies have Leukocytes in our blood to help heal and fix. I try to design "fixing" mechanisms in my programs to keep the overall program alive and running. Of course this guy is not as mobile as Leukocytes. He functions, more at crossroads like a traffic officer, laying in wait. If you can imagen that. Never happen, right?

Anyway, in programming I certainly have mechanism for detecting problems that potentially stop a program. I have "Time Watchdogs", "What ifs", and specific "Error Detectors". But what is new, is this guy is a "Representative". I have a bright interface that talks to me. He is only limited by my programming skills.

Late in the 1990's, I experimented with an "agent". Today, it would be more like an App. I controled a lot of Broadcast Equipment with code. But, I had an Agent that could modify code. I wanted to change code according to what had happened for the previous day. Up to this time, I had external files that recorded History, and were used to Programmatically alter the course of code execution. The files were a Reference for Parameters. This was easy and safe.

But what would happen if I could HardCode modifications? It is more like; "It is in the DNA." I had no trouble implementing the notion in principle: The main computer running the program would voluntarily put itself to sleep. Another program would analyse the code that was now shut down. And then make the tiniest changes, and at first were innocuous. That code would restart the main running code.

I had too many frightening experiences with this. Crazy things would happen. I would breath hard, and my heart would beat fast. I was loosing control. To this day, I can't believe I was playing with such fire.

Now that I am old, this guy is good for my health and ticker. The more errors I make, the more I get to see him. He is OK.

There exist the case of ERRORS in code writing, and in my case with this guy, the catching of errors is a little more dramatic.

RULERMAR.GIF, 1 kB

Five types of Notices:

Scheduled Events, such as appointments. Highest category. Timed Progress Reminders, starting 3 hours out.
During one of the Progress Reminders, at 1.5 hours away, a Notice Event is triggered. An acknowledgement is now required.

Calendar Events, such as Birthdays. Occasional picture and verbal information. Does not trigger any reminders.
Calendar Events are vocalised and displayed, and repeat every hour between SunUp and SunDown.

Triggered Alarm Events Triggers an Event Notice every minute, until Acknowledged.

Casual Notices and Remembrances, such as daily chores.
Triggers a Reminder Notice every six minutes, until Acknowledged.

Delayed Notices. I also call these Remembrances, that are deferred, and have no immediate action,
because they occurred during my sleep time. For example Weather Events that I will deal with later.
At 09:00 all delayed or deferred events are gathered, recategorized, and given to me.
Some of these deferred events will Trigger a Casual Reminder Notice every six minutes, until Acknowledged.

Here is an example of the lowest category.
No matter what big screen background, there will be this little pisky reminder screen, placed right on top of it, placed right in the middle.
Never anything to worry about. You can cancel it at any time, and it will go away.

This is of the lowest category. Like SleepTimes, pills and Garbage. Acknowledged by F2.

This is also a good time to point out the BackGround of the giant SunDial. The SunDial has no Time-Marks. This is on purpose. The girl reported that there were NO Events Scheduled. So specific hour marks on the SunDial clock would be inappropriate. Yes there was a minor Reminder about Spaggetti-Thursdays. But I could be there at noon, or one, or two. I do not want the shadow on any specific time.

But NO SCHEDULED EVENTS.

If there are No Scheduled Events, and
If it is the Week End, then
this happens once an hour, during daylight hours.

RULERMAR.GIF, 1 kB