Whoever at $supplier packed a label printer with thermal printhead and some standard label rolls (ie nonthermal ~ I’ve tested with a lighter) need to have his/hers/its head examined…
Did you give them a month notice? Is that customary there? Here, 2 weeks is the norm, and even then, you are often dismissed immediately.
2 weeks, and I’ve seen a lot of “negotiation” around either taking leave to run out the clock. I’ve also seen techs bounced around, as a previous employer didn’t want a tech to do server-level work (with the room to add in hidden accounts and such) so had him do desktop support for a couple of weeks. Or just paying a guy to sit around and maybe answer questions for a couple weeks.
I’m guessing Ook’s situation is there’s no real plan to replace Ook, and management is in denial.
Yeah, I get that. When I left my former employer ten years ago, I was asked to give training classes to the other techs on networking and such - all the computer-y stuff that the copier techs didn’t used to get into back in the analog days.
I was more asking if >2 weeks was the norm in South Africa. It’s been at least 15 days since he mentioned telling him that he was leaving, + he just said 17 days to go, = 32 days… kinda surprised me.
To a vendor:
Reply to all wrt resignations : contract stipulated a calendar month’s notice when resigning.
I received the notice and job offer round the 15th of last month, so it meant that I had to sit for a month and a half at current employer.
That is nothing. The one guy had to give two calendar months before resigning.
Yikes! . . . . .
Touched briefly on the touchy issue of me working on $sites with my manager, he support my view and also agree that he think I need to work supervised for the remainder of my time.
Work will be outsourcing my job, this is going to be really interesting.
1 Like
Sounds like this is CYA for you and him both.
1 Like
Dear $contractor
I’m not allowed to hand out passwords to cpanel, servers and the such. So you’ll just have to suck it up, I’m not going to change anything at this stage as I don’t want to change things, and then you’ll turn around and says something nasty after I’m gone here.
Suck it up and piss off.
I’m confident that ripping out a few hundred lines of code is going to improve things and si worth breaking things.
I love these guys.
This one is worth sharing.
Let Me Translate My Emails for You.
BY ADRIANA CLOUD
“I’m just checking in.” = Where is that thing you promised I’d have by now?
“Sorry to bother you again.” = Why can’t you do your fucking job?
“I feel bad for making you do this.” = You should feel bad for not having done this already.
“This was helpful.” = This would’ve been helpful two weeks ago.
“Sorry if I somehow missed your email.” = We both know you never emailed me.
“Thanks for the explanation.” = If you had told me this last week, you would’ve saved me a lot of time.
“Perhaps there was a misunderstanding.” = You didn’t fucking listen to me.
“I suppose that’s one way to go about it.” = Stop improvising and just do what I asked you to do.
“Sorry if my instructions were unclear.” = Are you a fucking moron?
“If you could get to this in the next couple of days, that would be great.” = Do this immediately if you know what’s good for you.
“I just want to make sure we are on the same page.” = I worry you didn’t understand my simple instructions and will fuck this up.
“I can’t remember if I already asked you to do this.” = I’ve asked you four times and you still haven’t done it.
“We don’t have a lot of flexibility in the schedule.” = You’d better get it done by my deadline or else.
“Let me know if you have any questions.” = Do not bother me with your stupidity.
“Thank you for your help.” = I would’ve done it much faster myself.
3 Likes
You called for help. Since you keep interrupting me, you can just wait an extra three hours.
1 Like
This integrated help system sucks! I could design something better in freakin’ HTML!
What I actually said: In six months I want to transfer to $softwareteam so I can share my ideas with them and hopefully make some improvements.
What I actually meant: I am going to transfer to that team and I am going to literally kill them with W7E discs until I am the only one left except for (ironically, given this forum) George, who can help me build a new Unix flavoured empire.
So you shifted the box from one public IP to another public IP without taking into consideration time critical toll road transactions. And then you sent me an email telling me That It Is Most Urgent to update the DNS records for said box.
And to whitelist port 80 egress for said box as equally important as the firewall is blocking port 80 for that box. What you watching? pr0nz?
Fuuuuu… haven’t you heard of EMAIL and COMMUNICATIONS?
Also, according to your latest email routing is borked on said source box - it is not my responsibility to fix…
Windows xxxx Home Edition cannot be joined to a domain.
End of discussion. Next time involve IT in your purchasing decisions. Now you can jolly well go and purchase a Winxxx Pro licence… not my problem now.
Kthanxbai.
1 Like
I remember having some sales weasel at a local shop try to tell me that it could. He argued with me until he ended up calling a manager over, who confirmed that it could, in fact, not be joined to a domain. 
2 Likes
I had a client that would, despite my recommendations, purchase Home Editions (XP, Vista, 7,8 etc), instead of the Pro editions. His Logic? "We saved $20 per unit!!!"
I try to explain that it took about 3hrs to jury-rig this PC to map drives, install apps, install printers , configure group policies, whereas an equivalent “Pro” edition would be done in less than an hour. We charge $125.00 per hour for Network integration.
So for every “Home” PC he bought saving $20 he paid and additional $250!!
I explained it to him EVERY time but he kept repeating the mantra "We saved $20 per unit!"
I felt guilty at first as I really don’t like overcharging clients but after a while I could see that I was wasting my breath. You can lead a horse to water, but you can’t make him buy Pro editions!
1 Like
This. ALL OF THIS. This is the kind of shit my old university would pull. Why aren’t the library computers on the network? Windows XP Home Edition. Why can’t IT003 talk to IT007 despite being next door? Windows XP Home Edition. Why can’t the lecturers log into the network? Windows 7 Home Edition.
Once upon a time in the year 2002, I was a (very green) IT specialist for a pharmacy group.
Pharmacists are a frugal bunch, so when the edict was passed to upgrade the PCs in $location, my mandate was simple: get three quotes, order cheapest.
The PCs arrived… with XP Home installed. I hadn’t thought to specify Pro. (Did I mention that I was green?)
However, given the main app we used ran under Novell NetWare and thus needed the NetWare client installed to log on, we were able to roll it out with very few issues (even printer sharing was handled by the Novell server).
I would never recommend installing the Home edition of any MS OS though, especially in a business environment.