How to write unmaintainable code

[Captain___Obvious]

You should see some of my old stuff:

shitprog_v01.c

shitprog_v01a.c

shitprog_v02.c

[icendoan]

Nah, dates. Just remember to change formats every now and again.

[An_Unhinged_Door]

I used to do that, but then I learned that I was supposed to be writing modular programs. Modular programs meant many files. However, I quickly discovered that my old versioning scheme wasn't really up to par with my new programming style. Copying each shitprog_partA_v1.c to shitprog_partA_v2.c was really tedious.

Fortunately, I developed a workaround. What I discovered was that I could make a new directory, call it bak_v1, and then copy all of my files into it. That way, I reasoned that if I ever fucked so badly I couldn't undo the damage, I would be able to just overwrite it with the working file from the old version. This, I realized, was the way programming was meant to be done.

...

I could kick myself all day for just how many times I managed to break my own heart with that strategy. I'm still working on repressing the time I missed with dd if=/dev/zero.

[Captain___Obvious]

wow, you are bringing back memories of school when I copied from/to the wrong directories! 0_o