MIM-cclxxviii ,Svenson


-- Home -- Links -- Sjon -- calendar -- Jobs to do --
-- Previous week -- This week -- Next week --


Tuesday

We had a load of cold (9C) rain in the morning and a few spells of drizzle during the day. Most of the time it stayed dray and even sunny.


Almost exactly one year ago (1998/10/01) the documentation for TeleSales was finished. It was then pulled trough a resource compiler to create Windows help files that were (manually) linked to the application. I did not yet work on TeleSales then. Since then nothing has been done to the documentation so the user manual and the online help are hopelessly out of sync with the application.

We got news today that a documentalist will be assigned to the project for three weeks to get the manual and the help redone. The person doesn't know anything about our application so we have to train him first and the intention is that we must keep the manual and help up to date afterwards so he must teach us how to accomplish that. Three weeks is of course ridiculously short. We spent the better part of the day just tracking changes in the screens compared to the screen prints in the current manual resulting in a 7 page listing of screen names. The best we can hope for is that the most used parts will be covered. Not because they are the most needed, quite the reverse is true a manual is important for things you don't do often enough to remember, but because that will be the part that is most likely to be checked.
Hey this looks like the documentation process used by Microsoft.

Before any one of the manual writers among the day notes gang smell an opportunity here, let me warn you, more than about 15 or 20 books, however good, will never be sold.

 

And the French reported a problem (via OLI) about the possibility to add phased out items on orders causing problems in the logistics module. They claim to do that by putting the phased out item on the second (or third or ..) line of the order. The first line traps the error. I tried to reproduce that situation locally but without success. I simply could not get a phased out item ordered unless there was still stock available, in which case there was no problem with logistics. I will have to check the on their system tomorrow because I don't have a user profile to log on with now. Wonder what they are doing different.

 

And there is, at last, a problem in America. It is not a problem of our making though. The logistics team has changed some common routines and added a server module. This was sent to America, amongst others, on Thursday. Some of the changed routines are used to convert commercial orders (TeleSales, OMSI3) into logistic orders (OLI). The Americans don't use OLI but a totally different product for their logistics so they changed the conversion routines, based on the old version, to work as a pass trough between TeleSales and their own logistics module. Because the new version had to do with OLI, a module they don't use, and because it came so late the Americans did not apply the changes to their conversion programs. On Friday we shipped a quick update to solve a totally unrelated problem but containing one of the affected programs.

With a little bit of assistance they found out where the problem was and they will correct things by applying the changes. That is what we call 'panic football' here in Belgium (for the Americans that translates into 'panic soccer' of course).


That is what one call an average day on the job. I didn't even have time to read more than Toms and Shaws day notes.

 

I got a reminder to pay an invoice that I already paid. They probably use a computer do the invoicing. So I am busy with paperwork.



-- yesterday -- tomorrow --


Svenson © 1999

Every day is different.