1. Code works
2. Add if statement
3. Code breaks
4. Comment out if statement
5. Code works
6. Uncomment if statement
7. Code works
8. Wtf??

I love it to maintain old unit tests which were not executed for about 5 years. 2/197 are green (╯ ͠° ͟ʖ ͡°)╯┻━┻

//TODO uncomment the following line if the Product Owner change her mind again this week....

*yesterday before I took a vacation

Siemens Step7 code block protection (PLC's).. It was designed to lock code that you don't want others to be able to read. All blocks are in a dbf file, so you just need to find the block record and uncomment one line, voila - source code available.

Given the massive use of Siemens PLC's on plants all over the world, and the simplicity of hacking via S7 protocol, usually Internet connected, it's a breeze to steal or modify the controllers code with possible critical implications.

Enter Stuxnet.

So I’m working on a project right and I don’t run it after writing 104 lines of untested code and it doesn’t work.

Which is expected but then I do some stuff and fix that, I get a new error which is great cause I’m getting closer.

Cut to tonight. I’m trying to hunt and kill this bug. And after doing nothing but copying the code to another text file so I can upload that copy and get help.

I decide to run it with a little just print statement in it to make sure it’s definitely broken and I’m not asking online for no reason.

And.. it works.. WHAT???

I uncomment the rest of the function and get rid of the print statement and scream because ITS WORKING!!

I MEAN IT HAS BUGS BUT THEYRE BUGS I CAN FIX AND FOCUS ON AFTER I FREAK OUT ABOUT IT WORKING AFTER ME CHANGING FUCKING NOTHING.

❤️ Swift ❤️
Compiling fails due to many inter-dependent errors (think database deadlocks).
1 - Comment the code that produces the "locking" error.
=> Code compiles.
2 - Uncomment the code that produces the "locking" error.
=> Code compiles.

My peepee hard

code not working?
comment code and try to run
uncomment piece by piece
code back to original
running...

apparently, the code didn't know it was right

I fucked up. I used the shebang line #!/usr/bin/env python3 in a script that was being ran every 5 minutes with a cron job. This generated an email to a system that dropped a file for processing and sent an age email for each file every minute. Because the Linux OS generated emails didn’t contain a keyword the script closed by design but I forgot to uncomment the delete temp file line. This started on Wednesday before a 4 day weekend. By the time I got in on Monday I was 40GB over my email quota and receiving 2500 emails a minute. I fixed the script and stopped the emails but down I have to clear out those emails. Here it is Wednesday and I am deleting 1 MB every 3 seconds. This is painful.

Picking up some uncomment code:

var_dump() and console.log() everywhere

1h later: shit I think I lost it again...

2h later: It was a 2-3 lines fix..

fml

I hate Intellij so much ...
* it has the weirdest bugs
* like window focus not working properly,
weird comment/uncomment short (jumps one line down wtf)
* It is slow as hell
* doesn't compile properly (or doesn't give a shit telling me about its actual status).
* Not even the build log is working properly. Why can I hide WARNs but no INFOs?? WTF
* Panels are all over the place and keep coming back, regardless how often I close them ....

ARG ARG ARG, *smashing face on the keyboard*

and the worst ... even though I have the F***ING ULTIMATE version, it constantly nags me about BUYING THE F***NG ULTIMATE VERSION AAAAAARG

Being mid-vacation and you remember you forgot to uncomment a 'file_put_content' line in a function for debugging purposes.. It's a script that runs 20 or more times within an hour and appends the entire script output to a file..

I hope the server can handle big text files..

Haven't recieved a phone call, so I guess it's still running.. :D

Anyone else notice that the error checking in Visual Studio sucks sometimes? I'll see the error pop up in the editor, read what it's complaining about, double check all the code, think for a minute, get confused about it, comment out some stuff - wait no, it wasn't that, uncomment it....

then save the file and it rescans. Boom, error gone. It was just a phantom error wasting my time.

Shure, I use version control. I use the UnR system. (Uncomment and rename).

Google codelab's logic :
"uncomment the code from a xyz function
run the test
test fails
uncomment the code from abc function
run the test again
test pass
Congratulations you learned test."
Well apparently this is not how world works Google 😥😌😴

When people use comments for build configuration. And don't put down handy comments like "uncomment this if you want to do that".
I guess what I'm saying is that this "code cleanup" task is turning into a "code keep the bloated baseline" task.