@funnyfish1982

I'm glad we have keys "ctrl" and "z" on our keyboards.

@mitsuefarnsworth2888

legitimately every archivist, curator, preservationist's worst nightmare.

@bobbymcgeeze7364

This scene is the most terrifying scene ever made

@AbraMacabreXx

That movie was so good lol. Whistlers mother. Mr bean kills me.

@raphaelsainte-claire4861

"well, it built on my machine..."

@darthalba3785

Saw this in the theater with my dad and we were both dying

@d3AdLyf3

I was in a room with sophisticated measuring devices. An observer grabbed a sphere bare handed and the engineer had a heart attack. You cant clean them, they sre that precise, and immense damage is caused by the stuff on our hands lmao.

@angie_2111

Mr.Bean: Good stuff in this can
Picture: zgzhfgxgxhz

@iskateFaIIen

That stuff cuts through auto paint….that art was doomed

@vegardjohansen9589

Thanks... Just took a break from coding because I got frustrated lol

@fastneuro9829

Just go back to previous commit

@wielkij8815

LOL accurate af.

@jbreward4035

Dude, one line of code can make things that fucked up🤣🤣🤣 so true

N/A

I was a wee boy when this came out.  I laughed so hard i actually wet myself.

Legit pissing myself laughing

@Simaris12

Even worse are lines in code that you know that they should not make any difference if they are in there or not (like a variable is set that is never used, or is not used anymore until program ends), but if u remove them, it breaks.

Someone found out this was a solution to an existing problem by accident and not knowing why himself, but it just works.

Most of the time such lines are commented in a way like:
"Don't remove. I warned ya."

my experience is: These comments are mostly to be taken seriously. Coding is 99% rational and logical, but there is still this 1% left.

@sajjad9qq576

I,ve told you not to mess with dam code

@watamatafoyu

Check local file history

@annguyen1454

Bro should learn SVN before coding.

@PRINCEXPRO-u5d

But folks say coding is fun....

@StynerDev25

😂😂😂