Error - Another user has changed this file. Would you like to save it, copy your file to clip board to compare, delete.
This is rubbish. I am the only one using this software at the moment and the only one trying to access this file.
Would you like to send an error message?
Yes - I would like to tell the programmer's new company that they are paying a lot of money for someone that knows nothing about programming!
I send the error message to my new, short on time, certified programmer and double click on the file again. I have found that if I repeat this process a few times, the file will eventually open to allow me to enter my data.
This is insane! And, for the first time in a long time, I am not ticked off and blaming Microsoft.
A few years ago I had this great idea - it was innovative, it was novel, it was something that had not been done in this large company before, and it was mine! I was going to automate a database for a specific program which would allow desk top access to everyone working that program.
At the time we had one programmer working with us - a self educated programmer at that. He needed hours, I had this exciting project, and we decided to start the ball rolling.
Never did he tell me, not ever even once, that he had no idea how to do the required programming.
A year after we started, we had a program that the users were, for the most part, comfortable using. Then... being the visionary that I am, I decided that I needed more administrative tools to increase ease of use and functionality. These advancements were for team use only - the normal user would not need to update their system.
And he changed it.
The night before he resigned.
And it is now 50% of what it once was such that I have not let my team update to the new system. Thousands of dollars, 2 years, and this is it!
He had a new programmer ready to take his place. I met with the new programmer He asked "how many people wrote this code?"
"Oh... (long silence)...It looks as if it were written by at least two. I will try and find the problems."
That was a few months ago. He is still trying to figure out why I am getting these error messages. I am now doing more work than I was before this project started.
I am a firm believer in ensuring that people know what they are doing, are honest about their abilities, and are doing work that someone else can do should they decide to leave.
The problem - my original programmer was improvising. Given his lack of formal training, he was tinkering and "making it work" rather than doing it correctly. My new programmer is having to decipher the code to formalize it to ensure that everything works properly.
Is it difficult for people to admit that they do not know how to do something? Is there some kind of humiliation involved with saying "I don't know?"
I learned, in my early twenties, that saying "I don't know" often provides an excellent opportunity to learn. I know that this guy was seduced by the challenge offered in this project. He used this project to get his bigger and better job somewhere else. That said, he might have learned more if I had known his limitations and been able to team him with an IT person familiar with the code required.
It is totally okay to say "I don't know!"