|
This level of developer laziness or passive aggressiveness is stunning. I aspire to live on this level.
|
#
?
Oct 3, 2019 00:11
|
|
|
|
| # ? Apr 27, 2024 09:34 |
|
|
That must have been done on purpose.
|
|
#
?
Oct 3, 2019 00:20
|
|
|
bobmarleysghost posted:That must have been done on purpose. I would charitably call it "lack of foresight". The reservation system itself is old enough that it was coded with lots of little weird space/memory saving tricks, because everything was on slow-rear end dialup and every kb sent counted. So for instance, the product data works on a rolling 10-year period, with 2020 replacing 2010. Best guess is that the dev who wrote the data export just didn't think about how it would work when the year rolled over, because the reservations system itself doesn't care.
|
|
#
?
Oct 3, 2019 03:26
|
|
|
"Nobody's going to still be using this piece of poo poo into the next decade".
|
|
#
?
Oct 3, 2019 03:33
|
|
|
A friend of mine once told me about a filing system he'd developed back in the 80s that would encode a document's relevant date into its 8.3 format filename. He managed this in part by using a single character for the month, so like a = January, b = February, and so on. I asked him "What about years with more than 26 months in them?" And for one brief, delicious moment his face registered horror
|
|
#
?
Oct 3, 2019 03:38
|
|
|
Data Graham posted:A friend of mine once told me about a filing system he'd developed back in the 80s that would encode a document's relevant date into its 8.3 format filename. He managed this in part by using a single character for the month, so like a = January, b = February, and so on. FalsehoodsProgrammersBelieveAboutEdgeCases.txt
|
|
#
?
Oct 3, 2019 13:30
|
|
|
Data Graham posted:A friend of mine once told me about a filing system he'd developed back in the 80s that would encode a document's relevant date into its 8.3 format filename. He managed this in part by using a single character for the month, so like a = January, b = February, and so on. A-L is month, MNOP is quarterly statements, Q-Z are year ends starting with Q=1985. What do you mean all the old statements are getting erased 15 years later?
|
|
#
?
Oct 3, 2019 23:46
|
|
|
There definitely was not a tiny network outage today. I most certainly did not forget a lab switch was hooked up to the main network. And in no way did I start messing around with STP, making the switch root. And I did not reboot the switch when I was done, cause that would have caused an STP re-election. Oops. Luckily, no one got mad.
|
|
#
?
Oct 4, 2019 22:17
|
|
|
BadMedic posted:There definitely was not a tiny network outage today. I am daily doing things that if I do slightly wrong, can cause stuff like total network outages, or entire applications to go down; most of us are. It's kind of a miracle that stuff is up as much as it is.
|
|
#
?
Oct 4, 2019 23:28
|
|
|
Thanatosian posted:Every time I think about it, I'm kind of amazed at how infrequently stuff like this happens. I often think about how as much as we try to architect for failure and plan for mistakes IT is often just such a house of cards waiting for one tiny puff of air to knock it over. That everything works as well as it does is shocking and I don't think users generally get just how many things have to work together well for them to be able to sign into email or something.
|
|
#
?
Oct 5, 2019 20:05
|
|
|
Our job is to trick rocks into thinking. I forget where I first heard that, but it sums it up pretty well.
|
|
#
?
Oct 5, 2019 22:41
|
|
|
22 Eargesplitten posted:Our job is to trick rocks into thinking. I forget where I first heard that, but it sums it up pretty well. We capture lightning in rocks and trick them into thinking.
|
|
#
?
Oct 5, 2019 22:46
|
|
|
https://mobile.twitter.com/daisyowl/status/841802094361235456?lang=en
|
|
#
?
Oct 5, 2019 23:11
|
|
|
SlowBloke posted:"Make a ps script to create each dyn group, with logging so you can be able to redo in case of failure or azure ad deletion." That, and a reminder that get-content/foreach is your ticket to productivity.
|
|
#
?
Oct 6, 2019 03:50
|
|
|
The variant I saw recently was "Teaching rocks to think was a bad idea"
|
|
#
?
Oct 6, 2019 14:50
|
|
|
No greater truth written.
|
|
#
?
Oct 6, 2019 19:03
|
|
|
Oh cool it's apparently OK to not know what to do next on a ticket and just leave it sitting in your queue for a week and not ask for help or let the requestor know what's going on. Who knew!
|
|
#
?
Oct 6, 2019 20:44
|
|
|
Welp one of the newer Windows updates, KB4524147, which was supposed to have a fix for the print spooler issues that a previous update caused, has actually made the problem worse. It has now broken the print spooler on machines where the previous update didn't break it. And for good measure has also broken the start menu on some machines. Came in today to 2 of our branch locations unable to print anything at all, from any machine.
|
|
#
?
Oct 7, 2019 14:01
|
|
|
Microsoft, welcome to the resistance
|
|
#
?
Oct 7, 2019 14:02
|
|
|
I had to reboot my work laptop AND the printer to get some poo poo to print, so this explains a few things...
|
|
#
?
Oct 7, 2019 14:05
|
|
|
Right now the only workaround is to uninstall the broken updates... or switch your printer drivers to Type 3. Type 4 will cause the spooler to crash repeatedly.
|
|
#
?
Oct 7, 2019 14:18
|
|
|
Aragaith posted:I miss that machine with it's 8 inch floppies and the ancient plotter that effectively had ink pens for its ink system. I worked with one of these. I’ve never been so mesmerized than I have when watching the robot arm scroll back and forth and up and down as it drew my massive network diagrams and (later on) Eve Online star maps. I worked with one that used static electricity to hold the paper in place as the pens moved over it and another that had a loose sheet of paper over a roller that moved the paper back and forth under a pen. This things were pretty cool. You know, for printers.
|
|
#
?
Oct 7, 2019 14:51
|
|
|
Welp it appears this same update is also causing no boot issues. I have one bricked machine. Gonna have to reinstall, repair won't work. Ugh.
|
|
#
?
Oct 7, 2019 14:53
|
|
|
Can somebody link the post the latest title came from? Somebody at my company earned infamy on a customer conference call. He was looping some new people into the bridge line and misdialed, reaching a phone sex operator and pulling them directly into the call.
|
|
#
?
Oct 7, 2019 14:55
|
|
|
BadMedic posted:There definitely was not a tiny network outage today. #s3outage2017 #dynamoDBoutage
|
|
#
?
Oct 7, 2019 15:05
|
|
|
I do wish people would replace 'I had to reboot to get x to work' with 'I had to mask the problems to get x to work, by rebooting', since that's effectively what they're doing. As an example, I was struggling with pxebooting to an NFS-shared filesystems over the weekend - specifically, I couldn't change passwords when a machine was NFS booting from an installation, but it'd work fine when I chrooted into installations root folder and changed the password that way - it kept claiming that the operation wasn't supported, and (d)tracing revealed that it was the a file-locking syscall (flock()) that was failing. So I looked a round a bit, and it seemed like most solutions on Unix-like platforms involve mounting with nolock as on option (FreeBSD is called nolockd). What this means is that locking is controlled locally instead of the server, but if a file should be touched on the server while it's locked locally, you instantly get both client-side and server-side corruption of the file (even on a filesystem like ZFS, because ZFS gets told to write corrupt data). The right solution at least on FreeBSD, meanwhile, is to run lockd on both the client and the server. Windows and Linux seems to require NetworkLockManger which is an entirely different kettle of fish.
|
|
#
?
Oct 7, 2019 15:26
|
|
|
D. Ebdrup posted:I do wish people would replace 'I had to reboot to get x to work' with 'I had to mask the problems to get x to work, by rebooting', since that's effectively what they're doing. I've been struggling with this at work for years. Our low-level support agents often go to "you need to reboot" as a plausible way to get people off the phones, no matter how many times we tell them not to. We even tried writing them up for suggesting reboots when it wasn't necessary. It ended up helping us get a paper trail to get rid of a couple of particularly lovely agents, but had absolutely no effect on those who were otherwise good at their jobs. They'd get a write-up, keep their heads down for a while, and when it expired, start rebooting poo poo again. I've given up.
|
|
#
?
Oct 7, 2019 15:54
|
|
|
lolol.. The official Microsoft recommended action to "fix" the printer problems they caused with this latest update is to reboot and try again. And then downgrade your printer drivers.
|
|
#
?
Oct 7, 2019 16:05
|
|
|
Printing deprecated, how will old people read email now?!?
|
|
#
?
Oct 7, 2019 16:14
|
|
|
Rexxed posted:Printing deprecated, how will old people read email now?!? Fax
|
|
#
?
Oct 7, 2019 16:14
|
|
|
ConfusedUs posted:I've been struggling with this at work for years. Our low-level support agents often go to "you need to reboot" as a plausible way to get people off the phones, no matter how many times we tell them not to. We even tried writing them up for suggesting reboots when it wasn't necessary.
|
|
#
?
Oct 7, 2019 17:06
|
|
|
Our helpdesk's present "fix all the things" is to run gpupdate and escalate when that doesn't do anything.
|
|
#
?
Oct 7, 2019 17:10
|
|
|
ChubbyThePhat posted:Our helpdesk's present "fix all the things" is to run gpupdate and escalate when that doesn't do anything. i love it when people troubleshooting method is basically doing religious incantations at the heretical machine. if their list of prayer commands does not work then the Mystery must be escalated to senior priesthood
|
|
#
?
Oct 7, 2019 17:19
|
|
|
Nuclearmonkee posted:i love it when people troubleshooting method is basically doing religious incantations at the heretical machine. if their list of prayer commands does not work then the Mystery must be escalated to senior priesthood Look the Machine Spirit is temperamental and I'm not gonna get executed by the Inquisition for going off-book. EDIT: I typed a command wrong and now a deamon has been summoned, escalating to Astartes Desk. Inspector_666 fucked around with this message at 17:30 on Oct 7, 2019 |
|
#
?
Oct 7, 2019 17:25
|
|
|
Our helpdesk's current troubleshooting method is to refuse to investigate reported systemic issues until enough people complain. It doesn't matter how reproducible the issue is, it doesn't matter if the NOC alarmed on it, they won't escalate to the SMEs until they get 5 user complaints. e: I've taken to just lying to them about the scope of problems just to make them act on it. My boss will complain all day about my methods, but there's no room to complain about my results. Renegret fucked around with this message at 17:27 on Oct 7, 2019 |
|
#
?
Oct 7, 2019 17:25
|
|
|
Renegret posted:F*x Please censor the F word, thank you
|
|
#
?
Oct 7, 2019 17:45
|
|
|
Renegret posted:Our helpdesk's current troubleshooting method is to refuse to investigate reported systemic issues until enough people complain.
|
|
#
?
Oct 7, 2019 18:31
|
|
|
ChubbyThePhat posted:Our helpdesk's present "fix all the things" is to run gpupdate and escalate when that doesn't do anything. Gpupdate /force has been our helpdesks go to first step for years. The other side of that is our group policies are so crazy it actually works a lot of the time to get things working again. 
|
|
#
?
Oct 7, 2019 21:00
|
|
|
Honestly we have so many computers that are left on for a week with a dozen people logged in, half assed custom apps that leak memory everywhere, and people running five hundred suspicious browser windows at once that rebooting is the only solution to most of our dumb problems. I mean training and decent programmers would also work but we're not doing that so reboots it is.
|
|
#
?
Oct 7, 2019 22:13
|
|
|
|
| # ? Apr 27, 2024 09:34 |
|
|
D. Ebdrup posted:It's impressive what meaning can be had from a dog going *pbbbbbbbbbbbbbbbbt* The olfactory meaning being 'maybe we shouldn't feed the dog bits of leftover pizza'.
|
|
#
?
Oct 7, 2019 22:28
|
|