Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "russian roulette"
-
A new way of making bad commits:
alias fuckit='git commit -m "$(curl -s whatthecommit.com/index.txt)"'
Its like Russian roulette with commit messages!24 -
Kids, dont try this at home.
[ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo *CLICK*
A.K.A terminal russian roulette.12 -
Me and my father at breakfast.
Me: Do you wanna play Russian Roulette?
Father: I boot up Windows every day. I already live the risky life.3 -
Got some customers not paying their bills?
Play russian roulette with these projects on the prod. server:
# [ $[ $RANDOM % 6 ] == 0 ] && rm -rf /<path_to_project> || echo "*click*"9 -
I curb procrastination by throwing in a random "sudo rm -rf --no-preserve-root /" to my test cases to see if I have unsafe evals. It's like Russian Roulette every test.1
-
How real men play Russian roulette:
realman@root:~$
[ $[ $RANDOM % 6 ] == 0 ] && rm -rf /* || echo *click*7 -
I got a friend who likes to travel randomly to random places.. he now found some dudes who share this hobby.
So now there is a thing running on my server ticking everyday, 10am, with a 1:150 probability to send a sms to 7 numbers (including me) which tells them to travel to budapest.
FYI: he and his friends study engineering, i study too. So 1:150 may sound pretty low at first but we don't have that much time over the year actually.:D
Russian Roulette Travelling is a thing now.😁11 -
Russian Roulette - Developer Edition:
Have a random generator for a number between zero and one hundred. Every developer present picks a unique number.
The generator must then reroll until somebody's number of choice is the result. It is now this person's responsibility to begin an untested deployment at 4:59pm the next available Friday.4 -
Hiring junior devs is a game of Russian roulette.
You can get some one who is smart and loves coding. In this case stack, limitations etc don’t matter and experience will be great for junior and the rest of the team
Or it will be a lazy person who watched 5 videos and think to be better than everyone else. 95% of juniors are these fuckers. Takes about 1 week to find out and fire… which starts the 3 months recruiting loop again.18 -
Outsourcing front-end for web is like playing russian roulette, but with 6 bullets in 6 chambers.
You shoot yourself in the balls (or ovaries)... HARD.
I don't know how you can develop in a complete nightmare of a SCSS file - 3500 lines of insanity.
This dev must have changed his mousewheel at least 50 times!
SERIOUSLY, why the fuck use SCSS when you piss everything into one single fucking file???
What drives me completely nuts is the fact that he even used an @import to include his custom.scss file... how many more IQ poins are needed to realize that you could SPLIT your spaghetti into smaller, sane files?
I need a whiskey...3 -
I'm so bored at work and need some excitement I'm playing Russian roulette on eBay... Making random bids on things I sorta want until I'm the Highest Bigger...
Then hoping I get outbid....3 -
Updating Windows from X build to X build it's like playing the Russian roulette but with the chamber full of bullets.2
-
I'm working on a laptop in the shop and Explorer crashes. I try restarting it, and get RPC endpoint call errors. On reboot, I get this.
Russian roulette but 3 will probably crash instead of 1.11 -
(another) Russian roulette for devs
$jobs -l
[1]+ 642 python .....etc
$sudo kill -9 642
.... other commands here
arrow up...arrow up... (looking for jobs -l)... got it.
arrow up...
$kill -9 642
F*uck! (i remember that i have not changed the pid)
kill: no such process (luckly no damages)
anyone killed something relevant making this mistake?6 -
class Bug():
def __init__():
self._fix = random.randint(1, 6)
def fix():
if self.is_feature :
return Feature(self)
else:
if random.randint(1, 6) == self._fix:
Bug()
del self
else:
return Bug() -
So today our informatics showed us how to download a file from the internet using Firefox.
It was BlueJ...
So he told us the people who develop BlueJ randomly include the JDK in BlueJ or don't.
He told us it's a bit like Russian roulette whether JDK will be included or not.
What he didn't know,
the standalone version for Windows obviously included it (.exe... ) and the version for other systems doesn't include the JDK.....3 -
I've been using Git since 2014. So why do I STILL cringe whenever I have to revert commits or do a hard reset back to HEAD? What's going to disappear? What will remain? Will my entire Git history be vaporized? It's a total game of Russian Roulette to me. So, without the certainty level I want, I just do what feels safer...I grab the versions of the files I think are what I need and stick them back into my repo, then git status and commit the correct changes back in.2
-
!!metarant
Every time I write a rant or a comment from my phone, and I want to temporarily switch to another app to search or copy something, it's a fucking Russian roulette.
Will there be enough RAM, or will Android stop devRant thus losing all my content forever? Let's find out! The gun is loaded.
(What about handling the full activity lifecycle like Android requires?)
Now, I would like to attach a picture of the feared "task switch button", but I'm too afraid to lose everything, so fuck it3 -
I'm wondering if devs would still play that russian roulette in linux if the one drawing the short straw gets it's GPU fried up 🤔
Or at least somethibg like that.2 -
What big set of fucken steel balls does one need to just clap your notebook without closing your porn?
-
I was sitting here and thinking about ways to make money with software! Then, i got this great idea: bashroulette / russian bash!
Play Russian roulette with your bash history:
https://pastebin.com/QsyDqme6
Prevent to fall in sleep in front of your desk. I got you covered!20 -
Hey EKS, it would be really cool of you if I didn't have to play Russian roulette with you when I try to scale down a node.
I cordoned a drained a node for you to notice, wouldn't it be too hard to let me select which one to put down instead of doing whatever you want?
Thanks.2 -
Let's play Russian roulette Developer version?
Let's write a PHP script to randomly drop a table in your database.... Hahahahahw2 -
apparently the chance of getting hit by an asteroid that nukes some large hole in the land or causes tsunamis everywhere is a lot more common than humans have seen lately
and asteroids come in chunks because they keep breaking up into smaller and smaller pieces until they finally disintegrate
and earth has had an awful lot of near misses the last 20 years so that means there's a bunch of chunks flying repeatedly though this solar system's gravity wells and we're playing Russian roulette every time, none the wiser
and it's not the asteroid itself that's really the problem though millions will die if one hits. it's that every time those things hit there's actual climate change
so then you'll have to survive sun block out, famines, and floods for like 2-5 years after
but the SPACEFORCE fired the guy responsible for planning for this due to DEI
how to win the game of geopolitics. know this information and hide it from the countries you want to die, wait for an asteroid, and they're unprepared and die. whoops wasn't us!4 -
Another part of messy network gone.
Caching fucked me hard....
Isn't it just lovely that nowadays you need to nearly wipe a machine to get it from claiming stale data....
And thanks to DNS, HAProxy -/ service names / ... I think I know now why the curse of babel is so powerful.
When you have to think for 2 mins to make sure you've set the zone's right, cause otherwise you need to ProxyJump with SSH through more tunnels than imaginable (VPN/HO) to fix possible caching on several DNS servers.... You'll realize that it's russian roulette with too much bullets. :(
And If a monitoring service asks another monitoring service for status information which asks the first monitoring service which then asks the second monitoring cause you were too late...
You'll get very funky monitoring statistics.
Too slow, had to nuke it (mismatched a DNS name, the second monitoring service should have been a service node).
I think I've had more near death scenarios in the last 2 weeks than I like.
Hopefully I'll never have to do that again.
(Splitting and reordering a few dozen VLANs, assigning proper DNS names, loadbalancer migration....)