Tangentially related, I remember at one of my jobs being tasked (several years in a row) with updating the copyright year in all our source files’ headers.
Yes, it’s actually to notify people who aren’t part of countries with membership to the WTO of the first available year of public declaration of distribution without restriction, however, putting “1997” on your website makes it look old so people put current year to make it look new.
It’s only legally distinct in Aruba, Eritrea, Kiribati, Micronesia, North Korea etc… so it’s almost entirely useless.
I meant it’s a red flag if someone can’t spin up the code and is making an intern change it by hand every year.
Tonight’s story: Every man older than OldMan.getMinimumAge() has been in perfect *unchanging* health for the last few months‽ To find out why, stay tuned! Our experts chime in to help you understand…
I don’t write documentation because I’ll be lucky to deliver the app 2 weeks after the deadline anyway, and I won’t be given any more time to document things, I’ll just be moved to another project or let go because it’s the end of the contract.
This happened at my work with internal docs as we switched from an ancient intranet to a new service that had a ton more features but no backwards compatibility so all the pages got updated to PDFs with helpful links that went nowhere and it caused chaos for like 3 months.
E2: of course that’s not why I told her. I explained how fastboot sometimes takes over and doesn’t actually restart the device, only “refreshes” the experience. I recommended she restart at least once a week. We’ll see what happens.
Idk how that person’s IT works, but in mine, that would probably warrant a lot of paperwork. The techs would have to pitch the change to client management, client management would have to pitch it to change management and provide test results to show it has no side effects, then deal with the techs complaining about the uptick in tickets about slow boot times or people justifying never shutting down or restarting with it taking so long to boot.
Not that they’re actually slow, our users are just super entitled. I got to observe the rollout of automatic screen lock for security reasons, and the ensuing pushback. The audacity of having to reenter your password if you’ve spent more than ten minutes doing nothing!
Security even managed to push for reducing it to five minutes after some unfortunate incident… but it got reverted for reasons you can probably guess. Hint: shit always flows downward.
I recommend looking into Windows hello for business to reduce the usage of passwords in the first place. It’s so much nicer to use your fingerprint, face, or even a PIN.
I would never consider fingerprints or face scans to be secure even for personal devices. I guess if theres literally nothing to protect, if thats possible.
I do understand the point that the biometrics are replacing very short pins usually, oftentimes 4 digits only but I dont quite see how that makes the passcodes worse than the biometrics.
I’d say even a 6 digit passcode with a randomized number pad, alongside an emergency wipe pin, would do better than biometrics, which also need to have a passcode setup as backup anyhow.
Maybe you could play out a few scenarios that illustrate your point?
Why exactly do you think biometrics are so terrible? Is it because you could theoretically access someone’s computer when they are sleeping or something?
As far as I’m aware that is not the consensus in the industry. I even need biometric (in combination with a card and a pin) to enter a specific datacenter.
I do think that bringing up specialised and uncommon hardware like randomised number pads is out of scope. Are you talking about highly sensitive and restricted systems? I’m talking about normal user computers.
Randomized keypads are for touchscreens, although like you said sort of not common for desktop workstations.
Just comparing a password to biometrics though on say a laptop or desktop, there is the major drawnback that you can be forced either knowingly or unknowingly to put in a biometric to unlock a device. It would be easier to circumvent then a standard password (at my company and the clients we work with, 16 characters is standard) with an encrypted hard drive.
This is all deduction ive made from other things I know to be true though, if you happen to know of a resource that explains both methods of securing g a workstation and the risks associated, I’d love to read it.
I also do agree overall that password less makes the most sense now, as people are never going to get better at making secure passwords and remembering them.
windows doesnt actually shut down, its some kind of hybrid hibernation now. it only really reboots if you actually reboot. so they may actually be “shutting down” every day.
They have successfully circumvented the reboot. I just always turn that setting off. SSDs are ubiquitous, nobody needs a fake shutdown. It just causes more issues.
At least in Europe the year after the copyright statement has no meaning, and even the copyright statement itself is useless. Since if not stated otherwise, no rights are granted by default.
Then you look at the uptime. 247 days. No longer have you been elevated. Now you’re the vilest of vile. You’re the user that lies. You just say what you think we want to hear, don’t you? Well, now you’re getting put on hold. For as long as your uptime was.
We have a running leader board for uptime. Servers don’t count. That said, I’ve seen some people who think they actually are turning it off but the machine just enters sleep mode. I only trust
unless you do it from a running system (which you shouldn’t, unless you want everything corrupted, that won’t help. windows has a feature called fast startup that only kinda shuts down your PC, even if you unplug it, so things that would get fixed by an actual reboot wouldn’t be fixed in your case
To be fair, I do IT for convenience stores. Sometimes we have to reboot pumps or similar, and all we can do is have them throw a breaker for 30 seconds lmao
Yup this is exactly what I was going to post. Was in the industry for 10 years and call me pessimistic but the second they told me they’d already rebooted I’d check uptime.
is a simple, non-recursive wildcard representing zero or more characters which you can use for paths and file names. ** is a recursive wildcard that can only be used with paths, not file names.
I had one where yes everything was plugged in but… The power strips never plugged into the wall… They were just plugged into each other.
That one turned out to be an annoying bit of cable management that I wouldn’t have had to do if they would have just left things alone and let me handle the original ticket
If I am calling IT to fix anything, it’s because I’ve exhausted all the usual things to fix it (restart, clear cache, make sure everything is seated, googled the issue, etc). 9 times outta 10, they’re just as stumped as I am and the device simply gets replaced. That 10th time tho it’s something I’ve never encountered but they have.
I would call IT and give them error codes and attempted remedies. They would do house calls and leave with a few rip its. Everyone in my office usually had my call IT because they (my coworkers and the IT guys) knew I’d at least tried something. If someone else from the office called IT, they knew that I was out of the office or the user was lying about something.
I support doing the troubleshooting yourself. Just be aware, if you call with one of those 9 out of 10 cases, we’re still going to have to do ALL of those steps again, so I can document that we tried them before sending any hardware. I’ve been burned one too many times by someone telling me they’ve already tried something.
I started in IT before switching to development. I have CCNA, A+, and Apple Pro certifications. I run Arch at home, btw. But when I have to contact IT, usually for something that needs elevated permissions or bad hardware, I’m just another user. It’s mildly infuriating to go through all the steps again, even after explaining what I did. I get it, I really do, but it’s not fun at all.
I tend to just check uptime before asking this question.
If I see the machine has been up for weeks and they tell me they rebooted it, I know i’m dealing with someone who doesn’t know that pressing the power button on the monitor doesn’t turn the computer off.
AFAIK fast startup only affects shutdown, clicking restart will always do a full reboot. Shift clicking shutdown will do a full shutdown like you said, but shift clicking restart will start recovery mode.
I explain fast boot to people by saying “for some reason Microsoft went and made the Shut Down button not actually shut down your PC, it really just puts it into a ‘deep sleep’ mode, and to their credit, it lets them say that boot times are faster… But it also means that in order to FULLY restart the PC, you have to click restart… I know it’s a pain”
Usually I get looked at like I’m from another planet, but that reaction means they’ll probably remember it later.
And sometimes fast boot (I’m assuming we’re both talking about the bios setting) causes so many blue screens in windows that it becomes almost unusable.
I just recently had a wfh user ship me one of his monitors back because we had exhausted every thing I could think of troubleshooting-wise. When it arrived I unboxed it, plugged it in and the damn thing worked fine. I followed up with him and finally realized he had been trying to push the damn power LED instead of the actual power button.
Searching for a button is sometimes really hard, as manufacturers are quite inventive. But then again, reading an instruction is usually an option even if it is last resort (in the list it’s right after mailing the monitor to the support, it seems)
I spoke with an incredibly nice Indian fellow, and he asked me to try some troubleshooting. I had done all of it before, so I… pretended. But I told him all of the things I experienced when I did those steps (and lied further by giving ample time to pretend to do things.)
He RMA’d it just fine in the end and it works five years later. But I did feel bad about lying. I just didn’t want to take my whole working setup and do the troubleshooting steps again D:
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.