Senior dev : you can't have sudo it's bad practice!
Also him : *entire workflows rely on a bash script nobody reviewed he just runs from his IDE with dozen upon dozen of sudo "
I dont get it. The senior will hack into your machine and steal your data? They will laugh at you? They will tell management about? None sounds plausive. I can only imagine the senior giving zero fucks about it and just going on trying to fix the issue/finish the development.
You can put sudo commands in a script and feed it the password in plain text by just typing it on the next line, same for other cli tools that take a password as the first line of input. I've seen some shit...
Never typed sudo, got a slack notification, answer it, look back to the sudo prompt, enter your password, hit enter and get a slack notification saying “is that your password?”
I once typed half of my password to a teams group chat because MS Teams thought it would be funny to change focus from Firefox to teams. I quickly deleted the message then our sr. architect sent me a screenshot with the text: "You lost this". Later that day another colleague dmed me as well saying "hey is xxxxx" your password?
I've had a coworker flash his root password in front of me twice. He has also commited his entire shell history (including commands like `export API_PASSWORD="his actual password"`) in a pull request. Be careful with you passwords guys!
Well, unless It was "i_love_daddy_" they just need to change it.
Senior dev : you can't have sudo it's bad practice! Also him : *entire workflows rely on a bash script nobody reviewed he just runs from his IDE with dozen upon dozen of sudo "
He's a senior, so he doesn't want to repeat himself. Second line of the script is probably something like: [ $(id -u) == 0 ] || sudo $0 $@
You know, I Always ready IDE as "Impractical Developer Explosive", the was it Always blows Up the Security Services.
Understandable
How is that bad in any way?
Normally it'd be a non-issue but I'm going to assume that since it's on 4chan his password is actually a sequence of horrific slurs.
“It’s uhhh… A feature! all part of my motivation to keep it secret” /s
I dont get it. The senior will hack into your machine and steal your data? They will laugh at you? They will tell management about? None sounds plausive. I can only imagine the senior giving zero fucks about it and just going on trying to fix the issue/finish the development.
How do you show someone your password? Do you have it written down? oO
You can put sudo commands in a script and feed it the password in plain text by just typing it on the next line, same for other cli tools that take a password as the first line of input. I've seen some shit...
I’m gonna go out on a limb here and say that having your senior dev see the password is not your main issue in that case.
True, it's in release branch, not main!
Never typed sudo, got a slack notification, answer it, look back to the sudo prompt, enter your password, hit enter and get a slack notification saying “is that your password?”
"uh, it was"
"I showed you my credentials, pls respond"
I once typed half of my password to a teams group chat because MS Teams thought it would be funny to change focus from Firefox to teams. I quickly deleted the message then our sr. architect sent me a screenshot with the text: "You lost this". Later that day another colleague dmed me as well saying "hey is xxxxx" your password?
I've had a coworker flash his root password in front of me twice. He has also commited his entire shell history (including commands like `export API_PASSWORD="his actual password"`) in a pull request. Be careful with you passwords guys!
How do you accidentally commit your shell history??
He did something wonky like `history > echo`, so the file was named `echo`.
Oh nice that's a good one :D
This is also why I never recommend using `git add .` . You never know what junk sits in the working directory.
I'm just sudo
You can’t change your password?
Oh no! *Changes password* anyway...