4 ms·

At my org the CIO knows fuck all about computers. Great guy on a personal level but wouldn't be able to quit Vim even if the lives of his 3 kids depended on it.

At my org the CIO knows fuck all about computers. Great guy on a personal level but wouldn't be able to quit Vim even if the lives of his 3 kids depended on it. He was put there because he was with the company for years before and he led other departments fine. Since he can't evaluate anything IT related himself he relies on 'advice' from the people beneath him who try to get the most budget for their departments by overstating how important they are. This layer beneath him is mostly product managers, RTEs etc... (We are SAFE Agile! Developer Velocity, Woohoo!). They also don't know much about computer and if they do it's very domain specific, such as SAP or so. These people try to fight for budget by overstating their importance. They demonstrate this by having more apps and more people relying on them. "Look we handled 2000 support tickets, the company would grind to a halt without us!". Never mind that having 2000 support tickets is a bad thing. And also mostly caused by their shitty apps. This keeps going on and on. I have 10 years experience as engineer and wanted to see "the other side" but it's so exhausting. A few months back a 'privacy officer' asked why the first and last names of our employees were in the Active Directory and ordered them to reduce the privacy risks. They failed to specify what risks. Couldn't articulate them even when asked. They also didn't say when the risk would've been reduced 'enough'. The team was panicking as they were now 'non-compliant' with company policy. I had to intervene personally to make sure this single directive didn't derail our entire company.

sgarland 7mo ago
> Never mind that having 2000 support tickets is a bad thing. And also mostly caused by their shitty apps. I’m constantly having to fight people to not add new, inactionable alerts as knee-jerk reactions to incidents. I swear the thought process is “an incident happened, we added a new alert - look, we’re proactive!” instead of, you know, fixing the root causes.
- apexalpha 7mo ago
  When WeTransfer suddenty changed it's policy for AI training last summer the entire CISO department panicked and had the entire website blocked. In traffic we could see that 12% of the company used the site daily, transferring gigabytes of data between our engineers and contractors. I asked why we didn't just start paying WeTransfer since it's so widely used and this would solve the problem, too. They said they should just use the internal SharePoint file sharing tool. I asked how this would work since most of WeTransfer use was us receiving docs, not sharing them. They said the contractors should just update their policy, and that was the end of the debate. Last time I spoke to a field engineer he said they mostly use private mailboxes now mostly since they "can't even copy something in Outlook anymore" on company laptops. I decided not to report this to CISO and these docs are workorders and pictures demonstrating workorders have been completed. They're irrelevant one day later.
  - rcxdude 7mo ago
    > asked how this would work since most of WeTransfer use was us receiving docs, not sharing them. You can do this in sharepoint as well. It's not the best, but you can make a link which is for upload-only to a folder and send it to someone so they can send you files without needing an account themselves. ...if it's not disabled by security policy like almost every other vague useful feature in a microsoft product seems to be by IT organisations.
- SenHeng 7mo ago
  I once had food poisoning after having sushi with colleagues. They very seriously wanted to have a debate about how we can prevent it from happening again. What? Am I suppose to never eat sushi ever again? Avoid possibly volatile foods before an important presentation? Understandable. Avoid sushi for as long as you're employed in this team? Fuck off.
  - greazy 7mo ago
    Haha that's next level insanity. This is why you build redundancy into very important things.
Quarrelsome 7mo ago
tbf quitting vim is extremely unintuitive to someone that opened it by accident for the first time.
- marssaxman 7mo ago
  I used `killall vi` from another terminal for years before I finally memorized the proper way to do it.
  - thaumasiotes 7mo ago
    How did you save the edits you made in vi?
    - marssaxman 7mo ago
      I didn't try to make any edits in vi; I just ended up there, on occasion, when something would invoke $EDITOR.
- SilasX 7mo ago
  Funny/informative story about this: There was a project, OpenHatch.org c. 2011 that tried to get people to be comfortable enough with programming to contribute to open source projects. In one of the tutorials (I think introducing command-line git?), if you followed the instructions, it would dump you into vim. It hadn't introduced to you vim by that point or explained that's what was happening, so you wouldn't even know enough to google the error. And this was a project that was supposed to be primarily focused on being newbie-friendly!
- budman1 7mo ago
  quitting vi is a basic competency test. would you listen to a doctor that could not suture a cut? how about a mechanic that could not remove a socket from a ratchet? simple file editing. vi has been around for every. if you haven't seen it, and needed it at least once, what have you been doing? (personal anecdote: once had an engineering VP bring up that a stray ":wq" in a document was a sign of a real engineer...working outside of where he should be..)
wpm 7mo ago
Your Active Directory is an attack vector. It would be safest if you shut it down :)

sgarland 7mo ago

> Never mind that having 2000 support tickets is a bad thing. And also mostly caused by their shitty apps. I’m constantly having to fight people to not add new, inactionable alerts as knee-jerk reactions to incidents. I swear the thought process is “an incident happened, we added a new alert - look, we’re proactive!” instead of, you know, fixing the root causes.

apexalpha 7mo ago
When WeTransfer suddenty changed it's policy for AI training last summer the entire CISO department panicked and had the entire website blocked. In traffic we could see that 12% of the company used the site daily, transferring gigabytes of data between our engineers and contractors. I asked why we didn't just start paying WeTransfer since it's so widely used and this would solve the problem, too. They said they should just use the internal SharePoint file sharing tool. I asked how this would work since most of WeTransfer use was us receiving docs, not sharing them. They said the contractors should just update their policy, and that was the end of the debate. Last time I spoke to a field engineer he said they mostly use private mailboxes now mostly since they "can't even copy something in Outlook anymore" on company laptops. I decided not to report this to CISO and these docs are workorders and pictures demonstrating workorders have been completed. They're irrelevant one day later.
- rcxdude 7mo ago
  > asked how this would work since most of WeTransfer use was us receiving docs, not sharing them. You can do this in sharepoint as well. It's not the best, but you can make a link which is for upload-only to a folder and send it to someone so they can send you files without needing an account themselves. ...if it's not disabled by security policy like almost every other vague useful feature in a microsoft product seems to be by IT organisations.
SenHeng 7mo ago
I once had food poisoning after having sushi with colleagues. They very seriously wanted to have a debate about how we can prevent it from happening again. What? Am I suppose to never eat sushi ever again? Avoid possibly volatile foods before an important presentation? Understandable. Avoid sushi for as long as you're employed in this team? Fuck off.
- greazy 7mo ago
  Haha that's next level insanity. This is why you build redundancy into very important things.

Quarrelsome 7mo ago

tbf quitting vim is extremely unintuitive to someone that opened it by accident for the first time.

marssaxman 7mo ago
I used `killall vi` from another terminal for years before I finally memorized the proper way to do it.
- thaumasiotes 7mo ago
  How did you save the edits you made in vi?
  - marssaxman 7mo ago
    I didn't try to make any edits in vi; I just ended up there, on occasion, when something would invoke $EDITOR.
SilasX 7mo ago
Funny/informative story about this: There was a project, OpenHatch.org c. 2011 that tried to get people to be comfortable enough with programming to contribute to open source projects. In one of the tutorials (I think introducing command-line git?), if you followed the instructions, it would dump you into vim. It hadn't introduced to you vim by that point or explained that's what was happening, so you wouldn't even know enough to google the error. And this was a project that was supposed to be primarily focused on being newbie-friendly!
budman1 7mo ago
quitting vi is a basic competency test. would you listen to a doctor that could not suture a cut? how about a mechanic that could not remove a socket from a ratchet? simple file editing. vi has been around for every. if you haven't seen it, and needed it at least once, what have you been doing? (personal anecdote: once had an engineering VP bring up that a stray ":wq" in a document was a sign of a real engineer...working outside of where he should be..)

wpm 7mo ago

Your Active Directory is an attack vector. It would be safest if you shut it down :)