pouët.net

can you give me ideas on what of a programmer's personnality may appear in his code?

except for the variable and function names... do you have ideas?

demomaking may be one of the programming that gives the most freedom to the coders, so i'm sure you may have ideas! :)


thanx!

(the global goal of this is to build arguments against software patents, so you may help a cause by helping me ;)

I might possibly be out of subject, because I haven't understood what it has to do with the reason you want it, but found it interesting that and how a code would reveal the programmers personality..

I would like to speak about my code. It's big, uncomprehensible and unreadable. Yeah it suxx and is preety indiferrent than usual codes. In some older quickbasic stuff, I was jumping up and down with gotos and using number labels. I still use goto on C, no matter if fishers establishment says it is not right! =)

Also I use crazy variables like shit7, tits19, ficken23 and stuff, when I get crazy with these nasty bugs!

Ohh,. and I love when my code is sooo chaotic! Definitelly shows how chaotic myself is ;)

I don't know to code OOP. Everybody is bitching about it and it has become a cassete player. And I gotta find a fucking job with that shit, ohh well.. :P
My C codes are still just one CPP file (When I download a foreign code it is raw CPP files and stuff and that just makes my mind messy. Ugh.. put all the shit in one thing! But I know it is supposed not to be good programming). One CPP or C with all the functions together in the same code and very chaotic stuff. No organization. Isn't that original for a C coder? :)

Asm too. I have seen Antitec's code on Z80 asm on CPC.

He doesn't like the way of others where they say:

mov dx,3C8h
xor al,al
out dx,al
inc dx
mov al,63
out dx,al
xor al,al
out dx,al
out dx,al

He prefers

mov dx,3C8h: xor al,al:out dx,al:inc dx:mov al,63:out dx,al
xor al,al:out dx,al:out dx,al

for example

You ve got to see his codes! Afteralls, they are sooo big (The code of our incoming(Since ages?) cpc diskmag for example) that if you did it with the first way (Each line one command) it would reach 1000 pages for example and when he would want to debug, he wouldn't be able. He would have to jump 50 pages beelow to see what the hell is going on on that jump! Hehehe.. (Wondering right now if Nasm has something to allow a command near the other, e.g. the : symbol, similar to the ; in C. It's a must I beleive! You have sometimes to squeeze the commands in the same line ;)

What else?

Just,.. I know I am out of subject but I had fun writting about coding personality. Won't help with the patents matter though ;P

Also I use crazy variables like [...] tits19, ficken23

So, YOU are the one coding all those pr0n dailers. ;)

hehe that's a funny example!

how code disposition can influence people read it and use it as a whole (thinking of the printout version of the whole code...)

the aim for all this is to prove that code is a kind of expression form, if not to say art form... to say that code is a pure representation of human ideas, and then, it comes obvious that patenting ideas is *bad* !

anyone may help me with examples of different codes doing the same things in very personnal ways (like you did!) for instance!


thanx!

"I don't know to code OOP. Everybody is bitching about it and it has become a cassete player."

This is sheer brilliance in its dadaistic purity.

Now I got the point about patents..
Interesting. I would like to hear more and more serious people :)

more, from more serious people I wanted to say..

there are no serious democoders.

well how my code can be identified with me:
* its always lazy and loose written, but always deadly cool

and thats 100% how i work IRL.

About coding, one of the most strange things are, that in C, there are three kind of coders.
- The first, wich open and close brackets this way:

if (something) {
do anything...
}

- The second:

if (something)
{
do anything...
}

- And the rest, who do it other way.

stefan: not to mention that both visuals and audio from you and your products suck.

anyways i suppose this is just a meaningless thread :)

RA5MUS: Please, don't be mean to stefan. Just say "it doesn't look like a high end prod"

;°)

My one attempt at coding ended up with me losing an arm and leg. I haven't bothered to look, but they still might be hiding in the source.

texel: only texas faggots and dogs insist on using a 100% fixed notation-ruleset. improvisation to perfection is the key.

I write something like:
if (something){do something; do some more; and more; and much more;}

..but not all the time ;)

rasmus: both visual and music tend to kick ass in my productions.

texel: i'm mostly nr.2 because i feel that it's mostly readable like that. but you forgot the else notations.

i write like this
if (bla)
{
} else if (plu) {
}

so it's 3 variants of C coders

optimus: writing like that is a tad hazardous but i'll have to confess on doing the same in macros.

steve-dave: no serious democoders, fixed notaion is for fags&dogs. geez, you do seem to have stuff to learn.
1: most democoders has jobs,and many in the gamebiz. eventho pcgames are crap, every coder that works with consolegames knows how important stability is.
ok we're not as always serious when pushing a demo for a deadline but as coders we're certainly serious.
2: fixed notation is good, i had no discipline when writing code when i started working. after working a while i automatically mostly write nice well-structured code. it doesn't take much more time and makes stuff more reusable(not wanted too often tho) but most importantly more easily extendable and more easily rewritable.

how about:

if (bla) do1(), do2(), do3(); else die(horribly);

whizzter:
1) i am a console gamecoder. even tho i know what i'm doing, i can't be arsed to be very serious about my democode. luckily that ain't required either, since compared to real-world stuff demos are plain simple shit.
2) i prefer "fixed", applying a strict ruleset on every situation is ridiculous and does *not* enhance readability, and thus has nothing to do with extendability and rewritability (two very important things, yes).

and it's funny how people call me steve-dave all of the sudden :D

whizzter, I use:

if (something)
{ /* and here I leave a blank space */
do(something);
}
else
{
do(other_thing);
}

My code that way occupies a lot, but for me is more readable.

I add a tab in the "do(...);", but this has not appeared in my post XD.

thanx to all of you!

all this about code disposition is quite obvious when you're looking to lots of diferent sourcecodes... what about some structural issues?

some types of data, or structures of programs, the way the tasks it performs are inter-related, etc... ?

do you know of some specific types of such structural items?

steve-dave:
i worked with console games(ps2,dc) for 2 years before starting school last autnum.
i'll combine 1&2 this time. yes,relatively to real stuff demos are sheit. however when i make libs to use with my demos and otherwise(3d,etc... ok i'm lazy but i focus more on the content). i'd want to re-use them and considering how sparsely i do demos it's been a blessing that i got my last demos done thanks to the wonderful simplicity of the lib i finished years earlier(being stoned&drunk doesn't help making demos as a coder :).
on the other hand the lib itself is unspeakably horrible so i'm afraid to touch it(i actually did a small mod last year)

texel:
we had a discussion about that at work, there's 2 points here.
1: yes, single brackets on lines are cleaner but your eye instantly catches the else. thus it's somewhere as readable.
2: when doing alot of custom cases (we used pure C) it's easier to confuse what's what

f.ex.
if (bla)
{
}
else
{
}
if (bli)
{
}
else
{
}
compared to
if (bla)
{
} else {
}
if (bli)
{
} else {
}

my syntaks is kooler than yours.