People Twitter

because they have never done it before, or to a very limited degree. why would you assume anyone knows how to ssh from a terminal? that's a very specific skillset. nobody is learning that at school.

using linux/unix has nothing to do with computer science especially today, vs 20 years ago.

maybe you use ssh daily your entire life, but that's not how other people do things. my research org has moved off linux/unix platforms to the point that our researchers only use ssh for legacy/archival projects. nobody is using it for anything after 2014. yeah, 10-20 years ago it was a ssh was a daily necessity, now it's like once a month or less.

all of our new stuff is web based. you login to a website and you access resources through the web, that way everyone can work remote and the infrastructure for those at home and in office and across the country, is unified and simplified and easy to access.

If there's no ForceCommand (I think that's what it was called?) in sshd.conf and no command=x in .authorized_keys (if any), you can probably use mosh. It spins up SSH to authenticate and then immediately start a UDP based connection afterwards. Instead of logging out every 15 minutes, you will get a "Last contacted X seconds ago" overlayed every minute, that's sure an improvement. Do note, however, that it keeps your shell running with no way to reattach to it if your machine turns off.

What if hacker steals the SSH key?

But to put all of that in context you have to remember the pay, which was also bad.

Lol the one I worked at had a 30% turnover rate because of this. Ridiculously skilled engineers working for a 8-14 month stint before they secured a much better job at a different company.

Even their longest working lead, who had joined since the start as a junior, left a couple of months after I joined

The funniest moment was when ~~HR~~ people ops posted the average expected salary ranges to confluence, which was a full 30% higher than what they announced for yearly raises.

Guess how we call this, but scaled up.

Honestly this one's on you, pal. Why do you even care about the megacorp's business?

I was in the corporate medical industry. The only things that got handled at all in a efficient time was those required by law. Like if there was a incident in the field we had to have an initial report within a week and a corrective action within 30 days. Preventive actions were longer term, didn't have a deadline so it was not uncommon for it to go on for a year or more.

I can't give a real example for legal reason but let's a product was sold which gave electrical shocks to a patient. Within a week we had to tell the fda the cause was a faulty resistor. Within 30 days we had to correct our system, for example assign a person to test that resistor with a dmm on every device. Easy enough, give the operator who installs the resistor a dmm, update the instructions to say to measure that resistor and give a 5 minute training to said operator telling them that they have to measure it. Easy to do in 30 days and required. Now really the root cause was we didn't test for that in our multiple automated tests. The preventive solution would be update the automated testing software to check that. That has no time limit. It now becomes low priority. We did have to give an estimated time line, say within 2 years. By the time that deadline approaches most people who originally said that have left the company and new people are unaware. They submit an extension, and it's low priority again. Another 2 years go by. Now the high priority is the next product release. The old product will be discontinued so no one cares. So for 4 years and possibly several more years after it the company pays a person to manually measure a resistor. The automated test would eliminate this need, be more reliable, have documented results but wasn't implemented because it's low priority since there's no legally obligated time line.

Sounds like Honeywell.

A Password is a thing that protects you from hackers. If you work here for long enough, you might even get your own account.

My first day was sitting for 8 hours abandoned in a cubicle because my new boss forgot to put in the new hire requests for IT. No user, no email, no nothing. Only reason I had a laptop at all was because they happened to find an old one in a drawer.

I was surprised by my current job. When I walked in the first thing they did was give me a badge to open doors. The second thing they did was take me to "orientation," which mostly consisted of them handing me a laptop and giving me the password for my already configured administrative user.

It's not always for lack of trying. I spent a year or so building the integration (from a box of scraps!) between the shiny new HR system and our IDP. This integration was supposed to be functional out of the box according to the HR system salesgoblin. It didn't just need to be configured, it needed to be built from scratch because they didn't actually support hybrid AD/Entra setups managed from the AD side. Which was only the unofficial standard for Windows based shops at the time.

Anyway, I wanted to make it grant employees access to shit based off a combo of Job Title and Department. On a technical level, it's basic baby stuff. Concatenate the Dept and Title into a string, use that as the key to a hashtable with the access they need listed. Bish bash bosh, bob's your uncle.

It would have been a cakewalk compared to all the shit I had to build for handling separations and all the data retention shit around those.

But none of the department managers could actually tell us what the fuck their workers needed access to. Like maybe 3% had any idea at all. And I didn't have the team or time to try and do data analytics across the access of everyone at the company just to get an unreliable best guess.

So it just handles setting new hires up with the basic access everyone gets and separations. Still a savings of ~1 hour per employee.

It's been something like 7 years since I built that integration. They're finally going to replace it with a true access management platform. It's cost them multiple millions so far, has an entire new department dedicated to the thing, it has been "in-progress" for two years, and it still hasn't replaced my shit yet.

My favorite part is when they come to me months in to something they're trying to get working, and I'm able to point them at where they made mistaken assunptions at the first step leading to the mess they're currently in.

I provided a ton of in-depth notes on our current standards, the weird gotchas/deviations, every single stumbling block and edge case I had found, all the seemingly logical and safe assumptions that don't actually hold. I don't think they read any of it. I keep asking them to reach out before they start working on a new piece of functionality. They don't.

So now I get to tell them things like "that assumption you built this piece of logic off of will bite you in the ass in this specific way", they say they'll take it under consideration, and I laugh knowing this whole project will probably implode under the weight of incorrect assumptions before it's finished.

heck, i had a consultancy gig where the customer wanted me on-site for intro 400km away, and i had to spend a few days with no hardware at all, never mind access. also it was a high-security thing so i had to be escorted around at all times until they could sort out the badge thing. very productive week, that. at least got a few hotel breakfasts out of it.

I have told my coworkers before.

The company does not make you take ladder training so you can learn how to climb a ladder, its so if you fall off, a lawyer can ask if you were following the ladder training exactly.

“Now we need you to watch 4 hours of videos to teach you how not to sexually harass everybody.”

The phishing testing at my company entertains me. They had to put in a mail header to get it past their own filters and we're not required to report them, we just get a lecture if we're tricked.

Someone put that all together and wrote their own filters to automatically delete them. They shared how to do so in a public room and now I imagine the only people who ever fail are new hires.

I set mine only to mark them read, not delete them, in case it got triggered incorrectly.

My dad was one of the guys who was in charge of administering those to his company. They had different tiers of difficulty, i think ranging from 1-5. They always sent IT and Engineering the 5s and they passed with flying colors.

Hr and finance never got harder than a 2 and they always fucked them up

Don't put that shit on IT. HR is the department that can't get the fuckin onboarding form right, can't send it to the right people, or just straight up don't do one and expect us to be mind reader's.