[ad_1]
It’s the same when those old big TV’s are not working properly so you hit on the back and then it suddenly works
[ad_2]
View Reddit by IdiotoftheEast – View Source
[ad_1]
It’s the same when those old big TV’s are not working properly so you hit on the back and then it suddenly works
[ad_2]
View Reddit by IdiotoftheEast – View Source
Best logic “If it works don’t touch it.” Heck don’t even put comments or you risk to fuck it. Happened to me once.
The official term for that is percussive maintenance.
As an electronics technician that needs to write my own programms 30% of the time I too know the logic of working Chaos. As long as you don’t try to improve it, it will not cause any problems.
I had to learn, that unit tests are actually really time and nerve saving…
“If architects and builders created buildings the way that programmers create code, the first woodpecker that came along would destroy civilization.”
I think this every time
My system ‘upgrades’ it’s software
If you work in support, you will soon realize that the next question is always “Why did it break? We need a RCA now.”
Nah, for scientists we’ve already spent a year making it work once so we definitely know why by the end. :'(
To be fair to programmers, you are trying to tell carefully organized sand what to do by zapping it with small amounts of electricity.
As someone who has repeatedly made the error to “touch it”, I can confirm this. Thank god for git.
Then you come back 2 years later to review your code and ask “Who the hell wrote this crap?”
Science: chemistry, biology, physics
Not science: social science, political science, computer science
You would be surprised how often in labs when we have a working method nobody wants to change it. Even if its an awefull amount of work to do it like that. Cause changing it and improving when its not the focus of the study would consume to much time and funding
As a programmer, can confirm. This is 100% correct.
There have been times when I fixed a bug, tried to optimize my fix and it broke again, then reverted to the code that worked before and it didn’t work any more. When it does finally work, you _do not touch it again!_
Once upon a time, I had an assignment in college, did it, it worked, all was fine. The day came to show it to the teacher, and it didn’t work! I changed random stuff, but couldn’t find the problem. As the teacher reached my desk, I had given up, and decided to at least show some extra stuff I made, since the main functionality didn’t work. But it worked. The teacher left, and it never worked again.
No need to touch it, next Windows update will fuck it up beyond redemption
Itt and OP: subpar level programmers likely.
What people on the user side don’t know is that programmers and IT are just all members of the machine cult. We sort of understand how all this stuff works but sometimes it just doesn’t want to like that, not until you call not until we ask if it’s doing x. The machines listen and wait for our call. The code works when it wants to not when we want it to. Would we be able to understand the machine as a scientist believes they understand the cosmos we would be elated. But that is not meant to be, we can only glean hints from the machines, find the rituals that fix them and adjust the rituals when it does not please them.
After more than a decade in biology labs, I feel like the bottom panels are more similar to scientists than anyone is comfortable admitting…
Yes, I want to answer hypothesis *X* but I always have to jiggle the handle to the PCR machine to make sure my reaction runs successfully, and that plate reader only gives good data after 3 pm. Also I put reagent *Y* in all my reactions with no idea whether it actually helps, but dammit I’m not risking changing it now!
To be honest, most scientists are not that far off from programmers….
I mean, we can always just use VCS to figure out how it worked and fix possible issues. If something breaks, just git reset.
The reason I *don’t* do that is because I’m a lazy asshole. 🙂
99 little bugs in the code.
99 little bugs,
Take one down, patch it around,
127 little bugs in the code!
Sorry but the scientist comic is also the programmer side for me
Look, I’m a programmer, and all I have to say is fuck those guys. If you don’t understand the code you don’t belong anywhere near it.
r/programmerhumor
If I ever had to say Sir at any place of employment, my sole use of it would be “sir, I quit”
Unfortunately… The truth.
It doesn’t help that the users of our custom software tools keeps FUCKING CHANGING SHIT WITHOUT DOCUMENTATION. So we the programmers keep getting called in because it must clearly be a fucking bug, and not the god damn IT guys who they should be going to first.
As a programmer, the best lesson I was ever taught was, “just because it works, doesn’t mean it’s finished”.
“percussive maintenance” 😎
Literally me in my IT job. You’d be surprised how often people mess with things that they just had fixed.
There’s another step to the programmer bit:
“Ah fuck now something else is broken”
Oh man, I had this problem BAD this week. I bought a new router and tried to hook it up. Didn’t work. No problem, I figure, I’ll just put the old one back in until I can figure out why. Old one doesn’t work. I contact ISP, they send a technician out the next day. He can’t get either router to work so he brings in a new router. He spends an hour and a half tinkering with it and talking to supervisors and customer service, can’t figure out why it doesn’t work. (I at least feel better that it wasn’t just me.) He puts in a ticket for another technician to come fix the problem. I get a message several hours later when the ticket is closed but the problem still isn’t fixed. I contact customer service yet again. They send someone out again, install a fourth router, and for no one know what reason the internet finally works. Now the router is in an inconvenient spot but I don’t want to move it to the other room for fear that it will take a week to get my internet back if I do.
Smacking the TV is called percussive maintenance.
That’s not how it works
Scientist: Great Job, now publish it as soon as possible and use the results to get the next grant. [Also go pray no one tries to reproduce it and debunks us](https://en.wikipedia.org/wiki/Replication_crisis).
Just light your incense and pray to the machine spirit before touching and sacred code.
I understand that under timepressure you dont want to screw stuff up by touching it, but my experience is that most programmers dont even care enough to try and get to the bottom of stuff. It’s painstaking, but its what ultimately will make you a better programmer, so dont skimp on it.