Technically speaking an event is a change in status. That’s not really inspiring, I know. But on the other hand, hitherto you got only half the truth. Because status changes are innumerable, and therefore you call an event only something which is changing a status AND (simultaneously) causing an action. That’s more tricky, I know, even in daily life. Because our digesting ability is enormous and sitting in front of the tv-set the procedure of absorbing huge piles of information without reaction becomes an important cultural skill. The weird thing is that in the media business, almost everything is an event and nearly nothing produces a status change within the audience.
No wonder, that in real life I sometimes feel like one of these old-fashioned schedulers, who can not respond dynamically to changing external data coming from business. So I remain sitting and eating junk, ignoring the data coming from the application (which is supposed to be the tv-program in my case).
The question behind is: when do I start thinking of a process not just as stupid external routine I cannot escape, but as something dynamic making me part of it? You wanna know the source of these thoughts? It was a white paper by UC4, which made me look Beyond Job Scheduling and the edge of my plate. Feel free to decide whether this event was user or system driven.