Sorry, you're a what again?
Jun. 8th, 2006 08:58 am![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
We're a large organisation. We have developers. The developers use PCs. And to show their egalitarianism, these PCs fail just as often as the PCs of the non-developer staff. The difference being that if you're a developer, you already KNOW about the unreliabilty of computer systems and as a professional, would have measures in place to handle unexpected failures, yes? You'd at least have a backup of your data, yes?
You'd think so.
So this developer's PC goes boom. It's reported to us, we pass it on to our vendor to go have a look at. Their turnaround time depends on how many employees they have in that town for the next couple of days, and how many other problem computers they have to look at first. We have no maximum turnaround time in our contract, you see.
The developer has been calling us every couple of hours asking where the vendor is, because (guess what!) the decided that the best place to store the only copy of their data was on the now-smoking crater of their PC. And it's SOOOOO IMPORTANT! They might have to WORK ON THE WEEKEND if it's not fixed NOWWWW!
Newsflash, sparky. You are not important. Your PC is not important. There's no guarantee that the hard disk will even be salvageable. If you, as a so-called professional developer, have not stored a copy of your work on (a) backup media, (b) a backup PC in your group, or (c) the humungous networked data store that you're supposed to store it in, that's your problem, not mine.
In summary:
1) No, I will not communicate your impatience to our vendor. They would only ignore me anyway.
2) Stop phoning and go and make yourself useful, if that's possible.
3) You have just been given valuable lessons about backups, redundancy, and your relative importance in the organisational hierarchy. In life, you will continue to be taught these lessons until you learn them.
4) Sucks to be you.
You'd think so.
So this developer's PC goes boom. It's reported to us, we pass it on to our vendor to go have a look at. Their turnaround time depends on how many employees they have in that town for the next couple of days, and how many other problem computers they have to look at first. We have no maximum turnaround time in our contract, you see.
The developer has been calling us every couple of hours asking where the vendor is, because (guess what!) the decided that the best place to store the only copy of their data was on the now-smoking crater of their PC. And it's SOOOOO IMPORTANT! They might have to WORK ON THE WEEKEND if it's not fixed NOWWWW!
Newsflash, sparky. You are not important. Your PC is not important. There's no guarantee that the hard disk will even be salvageable. If you, as a so-called professional developer, have not stored a copy of your work on (a) backup media, (b) a backup PC in your group, or (c) the humungous networked data store that you're supposed to store it in, that's your problem, not mine.
In summary:
1) No, I will not communicate your impatience to our vendor. They would only ignore me anyway.
2) Stop phoning and go and make yourself useful, if that's possible.
3) You have just been given valuable lessons about backups, redundancy, and your relative importance in the organisational hierarchy. In life, you will continue to be taught these lessons until you learn them.
4) Sucks to be you.