We had somebody melt a laptop power cord with their Space Heater.Quote:
At least when people do something COLOSSALLY stupid, there's no chance it can blow up an entire city block.
Printable View
We had somebody melt a laptop power cord with their Space Heater.Quote:
At least when people do something COLOSSALLY stupid, there's no chance it can blow up an entire city block.
I had someone put a CD on top of one of those candle warmers - then put a candle on top of that - citing that "it got too hot and melted her candle too fast".Quote:
Originally Posted by Melcar
The smell of burnt plastic didn't go away for almost a month.
Oh yeah, our CSR people wonder why they have issues with their computers, and we tell them it's because their space heaters are blowing directly on them. We had one temp melt the face plate of an older Dell desktop. It's funny now, but it damn sure wasn't then. We've also tried to unplug the heaters from power strips and found them to be pretty much welded in.Quote:
Originally Posted by Melcar
Are the buildings poorly heated or something?
In their defense the entry door is an automatic sliding door, and in the winter (although our winters are by no means that cold) they do get cold air coming in at them.Quote:
Originally Posted by FilanFyretracker
Relevant article: http://www.wired.com/2015/08/men-wom...ce-thermostat/Quote:
Originally Posted by FilanFyretracker
Yes, especially with HVAC zones. One person will be warm so open their window which will trigger a call for service for the thermostat which will cause the heat for that zone to trigger which heats up 5 other offices. Or the person with the thermostat in their office will run a space heater which will satisfy the thermostat so there will be no call for heat - so then the surrounding offices freeze.Quote:
Are the buildings poorly heated or something
I bet each port lacks an open close function on the grille register as well.
Yup.Quote:
Originally Posted by Tinthalas Tigris
My building, with a capacity of about 220 people, has 7 or 8 AC units on the roof.
At any given time, they may be completely non-functional or working at sub-optimal efficiency. Only the one that powers the switch closet/server room is worthy of a service call (even though service calls are FREE during business hours).
Everywhere else, the ducting is weird, the vents are in some of the WORST possible places, and even though all of the thermostats are set the same throughout all cubicles and offices (and digitally locked) there is a 15-20 degree difference in temperature as you walk around the office on any given day. Sometimes a 25 degree difference (Yes, we have had one area at 62 because the most powerful vent was away from the thermostat and the thermostat was catching afternoon sunlight, and another at 88 because the thermostat was right under the most powerful vent away from any windows) and that doesn't even count the time someone left the heat on until mid-september on one thermostat, which didn't register it because the conference room right next to that one has independent non-locking non-digital thermostats that were set to "meat locker" so the projector bulb wouldn't blow. (It hit 53 in that room once. It was AWESOME)
I find that 99% of the time, in office buildings, the problem is REALLY, REALLY POOR FLOOR PLANNING with regards to thermostat and vent layout.
Somehow I always end up in the "limbo cube" where no cold air ever reaches and it's always the super skinny folks who hate the cold that end up sitting *right* under the strongest vent in the building.
Some days I just move my work to the server room. I'd much rather be shivering than sweating.
Pri 1 URGENT CRITICAL ticket goes into queue...assigned to a team that is not mine.
I notice nothing because I'm working from home on a project.
Person entering ticket gets irritated that noone has responded and CALLS ME AT HOME.
Being the loving person I am, I answer, find the ticket number, and here's where the WTF begins.
The cast:
C: The caller, who works in sales engineering and closes multi-million dollar contracts.
M: Me. The guy who works in IT supporting the people who earn us money.
F: The particularly nice guy who happens to work on the firewall team.
C: I put in a ticket because I can't log into the website we use for all of our product sales and ordering.
M: What do you mean you can't log in?
C: I can get to the main page, but when I hit the login button, nothing comes up.
M: Okay, let me try...yep, works for me.
C: Can you come over to my desk?
M: No, I'm working from home.
C: Oh, that's why it works, you're on the VPN.
M: I'm sorry, what now?
C: Other people around here are able to use it because they have the vpn client. They're all on laptops. I have a desktop and so noone ever installed the vpn client for me because I'm not taking this thing home.
M: Okay, this ought to be interesting, let's try installing the VPN on your machine. *installs VPN client* Okay, try it now.
C: Yep! It works.
M: O_o
C: Hey can you help this other person? She doesn't have the VPN client either.
M: Sure! *helps other person*
M: *does background checking*
M: *calls firewall guy*
F: Yo!
M: Okay, can you think of ANY reason that everything on these two subnets going out on the LAN *only* are blocked from accessing this site address while it works on wireless and VPN? *gives site address*
F: Well the...Hold on.
M: *holds on*
F: Okay, found it. We applied the vendor supplied blocklist to that brand of firewalls. Only the LAN traffic in that office goes out from there, everything else is on (other brand) or (other other brand) so that's why it only affected the LAN traffic in that one office.
F: I've gone ahead and amended the vendor-supplied blocklist to allow that IP. Can you have someone test it?
M: hey C, can you hit "VPN Disconnect" and close your open browser window and try to login again?
C: Yep...Okay, it works now!
M: Cool, thank you, have a great day!
M: Yeah, F. It works now. Thanks.
F: No problem!
/facepalm
WHO THE FUCK PUTS IN VENDOR SUPPLIED FIREWALL RULES WITHOUT TESTING THEM FIRST?!?!?!?!?!?!?!?!?!?!?!?!?!
So the product manager finally got involved and is forcing QA to retest the recent builds of the Program4-Sub-Print executables.Quote:
Originally Posted by Mileron
I got to have the following conversation with the QA manager:
QAMgr: Were you able to reproduce the issue with the Program4-Sub-Print executables (without manipulating the underlying files)?
Me: I'm not completely understanding your question
QAMgr: When we report bugs in QA, we must provide the steps to reproduce the issue. That's what I'm asking for.
Me: That's what's in the big long email I sent you yesterday ([i]which the thread starting with what I sent in this post)
QAMgr: Those are not steps and we wouldn't put that in a bug ticket. How did the client produce the issue? It should be pretty straight forward.
Me: They updated the Sub-Print program, opened the Print window, and were unable to have users of a Senior level make any changes to the print options
QAMgr: What I'm not understanding is why the dev couldn't reproduce it and neither can my testers.
Me: Because they're not starting with the right conditions of the user login tables, probably, which is what my email covers
QAMgr: If they update the Sub-Print program and open the print window, they should see it. We are missing a piece.
Twenty minutes later, during which I'm guessing she actually read my email
QAMgrSo, prior to updating the format, we need to have a Senior level user.
Me: Correct
QAMgr: What was the last working version of (state-specific) Sub-Print executable please, where this issue did not exist? ...if you know it. If you haven't checked that one, we can figure it out.
Me: Haven't checked, but it would likely be whatever 2015 release was latest
QAMgr: Ok, we'll start there. Thanks.
Been there plenty. As the supervisor as well as the guy reporting the error.
On the supervisor side, I totally understand where he/she is coming from. The majority of things that come along your desk are errors that occur during beta/testing phases and it is your job to delegate who will fix it, and why the error occurred in the first place, and if that job even involves parsing code, it is typically just going back and forth between two screens of revisions, trying to isolate where it occurred before passing it on to someone else to fix.
Something like this sounds like it has been in the code for a while and just finally became a real bug, one that they didn't properly test for.
So now, the QAM needs to follow his/her protocol of discovering how you found it while keeping her butt from getting into trouble (if at all).
QAM ussually gets these errors handed to him/her when it isn't an actual error, but an oversight of someone who wasn't documenting the error properly and has to hand it back down to someone else to fix (as well), before giving them a lecture of sorts in order to tell them how to properly isolate and fix these kinds of things before they get to their desk.
There is a limited possibility that someone in the testing line admires your efforts and didn't bother to touch any of your feedback before sending it on to the next monkey, and so on and so forth. When it landed on the QAM desk, that person was confused as for why so much data was in their lap and after line 4, or 5, decided it would be better to talk one on one with whom they were dealing with.
You certainly did nothing wrong, and this being something that doesn't happen often for them, wanted to know how it happened and see it replicated in person before spending the time to read an e-mail that could just be another folly.
In your case, you did absolutely everything right, and maybe, possibly, but probably not very likely, will be commended for this type of documentation. It doesn't happen often. It probably will not happen in your case, because QAMs would much rather keep the praise and prestige within their own team.
Hold your head up high, dude. You are the bastion against the software apocolypse.
I get an email from my office's local IT group...
LIT: Yo, remember how you used to have that floor model cooling AC unit in your old office? We have one that we need help with. Can you come over for a bit?
I head over to the local IT office, which for the last 14 months I've been pretty much banned from due to my "attitude" back when my server started to shit the bed and all I wanted was my local IT to help me.
Anyway, I go over and I'm escorted to a small hardware closet. It's maybe 8 feet by 20 feet and houses a half dozen racks full of network switch and VOiP telephony equipment. And it's HOT.
There's a standalone AC unit in the corner, plugged in, cooling tubes pointed at the racks... venting back into the room via a coiled, stacked exhaust tube.
Me: I'm not understanding what I'm supposed to do here.
LIT: Make it cool.
Me: Outside of the fact that I'm not HVAC certified, what do you want me to do?
LIT: Make it cool.
Attachment 4862
Me: Go get me a PC box and some packing tape.
LIT returns in a few minutes with a box and said tape.
Me I take my penknife out of my pocket and cut the box, breaking it down completely into one long sheet of cardboard. Then I tape the flaps together, tape one side of the box to the edge of the door, and drag the AC unit closer to said door. I tape one side of the exhaust tube to the door frame and haphazardly seal the box to the door frame and tube.
LIT: See? You fixed it.
:wtf: I seriously wish I could have recorded that.
That.
Picture.
Is.
PERFECT!
You seriously could not have picked a more apropos image.
I totally forgot about the Pakleds.
:rofl:
They looked for things that made them go, and they settled on the Planet of Prunes and Cranberries.
Better than how I'd have fixed it. I'd have cut through the sheet rock and vented it that way.
Also why when setting up that office did the company not tie in a supply and return from the main AC or put in a minisplit?
Coworker: "hey, we are out of compound A, and I need it in building 770 immediately."
Me: "well, go get it from the 720 building"
Coworker: "No, we're out."
Me: "what about the storage at 5225?"
Coworker:" we are completely out. "
Me:" how long have we been out? "
Coworker:" for a while, i just didnt need it until now. "
Me:" you should have told me before we ran out. "
Coworker:" well, you told me to tell you when it runs low. "
Me:" did you? "
Coworker:" no. "
Sent using TAPATALK via Android
This one was actually a week or two ago:
My laptop has been not working right for the past 6 months. what can you do for me?
Me: "Bring me the laptop & I'll take a look".
But I need it today!!!?!?!?! Can't you just like....
Me: "are you fucking kidding me?"
"my phone doesnt't work any more"
Me: need more details
"it just doesn't work"
Me: ok bring it to me and I'll have it replaced.
What shows up at my desk is the remnants of a Gigaset SL3 that has been dropped a dozen times too many, fixed up with tape, and dropped a few dozen times again over the course of five years.
I shall post a picture later. Got one at work.
No edit so here we go, old vs newQuote:
Originally Posted by Ronaan
http://uploads.tapatalk-cdn.com/2016...0148b28a8e.jpg