Looking back at your old code

I just happened to look at some code I wrote in 2007 and haven't touched ever since. Now it seemed embarrassingly bad. That made me feel good; I've been programming since the early 90s, and apparently I'm still making measurable progress in such a short period.

Any similar experiences?

the only thing you are making progress towards is self-destruction. how's that information make you feel?

I'm definitely improving. Looking back, it looks so terrible. I can't believe I actually thought some of the things I did were a good idea. I know I'll never be perfect, but I don't like that feeling that I'm currently doing something fucking retarded, but I won't be able to appreciate it until 5 years later.

the other day I read an old implementation of a database manager I made when I was 16 using mother fucking PASCAL
shit is fugly

>>4
Haha, I remember when I read my 2000-line game written in Turbo Pascal back when I was 5. Apparently I didn't know about indentation *blushes*

The most I've ever done is Red Alert 2 & Yuri's Revenge mods.

Feels good though, that shit could generate a lot of bugs.

I used to code

with
{
    this indentation style
}

Which I can't stand. So now I

use {
        this indentation style
};

I usually rewrite old code if it can be useful, but sometimes that shit is so bad I can't do anything.

>>6
yeah, YR is terrible to mod.

i used to code like this:
herp{
derp{
irc{
for{
}}}}

Thank god that's over

>>8
had that same problem with a secondary language compiler i wrote for a language i invented called PuBL

>>7
so you got worse?

>>12
That's K&R, dipshit.

>>13
As i said, you got worse.

>2 indent is horrid to read

>>1
I know that feeling.

>>5
I wish I had some of my babby QBASIC;  thinking back it feels like I was never more productive.

>>15
My first non-trivial program was a stick-figure rendition of Street Fighter written in QBASIC. Then I got a faster computer the game became unplayable. It's surprising how oblivious to vsync even many "professional" programmers were back then.

>>16
vsync is separate from processor dependent program speeds. Vsync is about prevent the graphic buffer from being drawn to or read from more than the refresh rate per second, thread calculation limits are more related to preventing unnecessary, it's more like a vsync for logic rates in that case.

I guess if you get into the technical aspects you could probably even make a way for the rendering methods themselves to halt, consuming less gpu power, though it's probably safer just to lock a transfer buffer. I'd be interested if someone had insight into how or what OpenGL or DirectX specify to happen when vsync is enabled, and what the various gpu driver makers actually do

>>17
preventing*

preventing unnecessary consumption*

>>1
No, it means your code is always bad but you don't realize it until you look at it again with fresh eyes.

When I look at old code, I'm often amazed by how good it is. Sometimes I'm afraid I'll never write code that well again, but then I continue to amaze myself.

>>19
Behold! The Sussman!

>>20
:DDDDDDDDDDDDDDDDDD

>>19-21
faggots, all of you