![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Once there was a computer system. It was an old mainframe system and had been designed and developed in Australia. It didn't mind much about incorrect batches, or odd material numbers, because it took the overall view that "It'll all work out in the end" - an overall attitude of lassaiz faire, although it would never have used such fancy language to describe such a thing! It was easy going and undemanding, and, for the most part, it worked, and its users were accustomed to its foibles and its follies.
Then, one day, it was replaced. Its successor was a client-server system originally developed in Germany that had been around for probably as long as the old mainframe, but which was considerably more complex and complicated. This new system required precision and dedication to detail. This material with this lot number was loaned out to Customer A, therefore it must be received back from Customer A before it could be sent back to Customer B. The same material with another lot number will not do because where is that material now? How can the system keep orderly records if the data comes back in such disarray?
And, lo, the users accustomed to the old system were Not Happy, Jan! And they did complain in great and multitudinous numbers as they learned to use the new system.
Unfortunately for the users, the new system with it's Germanic precision and organisation was here to stay. No haphazard 'tumble it all together and the white and colours will sort themselves out' thinking any more! No more 'she'll be right, mate' attitudes! No, it must be careful attention to detail and the necessity of playing by the rules - crayon marks within the lines - within, I say!
And, lo, it was a big headache for the little programmer sent far from home to help troubleshoot in another city.
tl;dr: I have a headache from dealing with the users learning to use the new system. The system is easy enough; it's the mentalities of the users that's hard to change.
Then, one day, it was replaced. Its successor was a client-server system originally developed in Germany that had been around for probably as long as the old mainframe, but which was considerably more complex and complicated. This new system required precision and dedication to detail. This material with this lot number was loaned out to Customer A, therefore it must be received back from Customer A before it could be sent back to Customer B. The same material with another lot number will not do because where is that material now? How can the system keep orderly records if the data comes back in such disarray?
And, lo, the users accustomed to the old system were Not Happy, Jan! And they did complain in great and multitudinous numbers as they learned to use the new system.
Unfortunately for the users, the new system with it's Germanic precision and organisation was here to stay. No haphazard 'tumble it all together and the white and colours will sort themselves out' thinking any more! No more 'she'll be right, mate' attitudes! No, it must be careful attention to detail and the necessity of playing by the rules - crayon marks within the lines - within, I say!
And, lo, it was a big headache for the little programmer sent far from home to help troubleshoot in another city.
tl;dr: I have a headache from dealing with the users learning to use the new system. The system is easy enough; it's the mentalities of the users that's hard to change.