The planning makes me sleepy
Although we all use computers, few ever face the challenge of having to program the software. Good thing. It takes a certain kind of mind to work through the possibilities and fit the squeaky parts into the right spaces.
Let me give you an example, based on the current project that our resident programmer is trying to complete. From where I sit, all that I can think of is “fitting worms into a can”.
We have two groups of employees, each falling under the rules and regulations of collective agreements. In the case of some “doing” overtime, there are things that one must do in order to receive just compensation.
Consider the following. One fellow stays after closing time to complete whatever is required. In return for one hour of time given, one-and-one-half hours will be accorded at a later date. Another fellow, with a different job description, stays on late. He will receive one hour for one hour, up to a maximum of five hours in the week. The sixth hour turns the whole thing into the “time and a half” model. Both require approbation before starting, and a further approval upon completion.
In the old days, there were forms to fill out. Easy.
Now, the plan is to computerize the whole thing, and the approbation/approval steps will generate a set of email messages. The whole online form should work in two languages, and the updates to the master database cannot be corrected or erased. The input should be on a regular basis, and the reporting system should be simple enough to allow any administrator to handle the workload (sic). And the analysis, coding, testing, documentation and implementation must occur within a set period of time, due to budget constraints.
And, the planning can be interrupted at any time by someone in HR thinking of an added feature set.
I am so lucky to not have chosen programming as a career path!
