Writing clean code in C

So how do I do it?
C is supposed to be a good and fast language, but all the programs I make end up being clusterfucks of unreadable code

>>37
MIPS doesn't have hundreds of pages of legacy garbage and short-sighted decisions like x86 does.
LOL. Anyway, you're completely ignoring the commodification of 3D hardware. Towards the end, SGI didn't offer anything you couldn't get somewhere else.

>>37
The bootloader does away with 16-bit mode. The only time you might encounter it is if you want to write a 16-bit interpreter for BIOS code in order to interact with the old BIOS interface, which you shouldn't because EFI is there. The legacy garbage is the manufacturer's problem, not the programmer's.

Thread then: Hey guys, how do I write clean C code?
Thread now: HURR MY CPU IS BETTER.

>>43
Thread then: Hey guys, how do I write clean C code?
Thread now: Butthurt Jews don't want to admit that Intel Jew chips are trash.

>>44
Thread then: Hey goys, how do I write clean C code?
Thread now: Butthurt Goys don't want to admit that x86 is master race.

>>45
You don't even know anything about x86. Go suck Shmuel Eden's 16 nm penis somewhere else.

>>28
gcc -c -ansi -Wall -I./include read/prog/1328166396 -o obj/prog/1328166396.o
read/prog/1328166396:>>28:71: error: ``guess what?'' is not a question.
make: *** [obj/prog/1328166396.o] Error 1

>>46
I know x86 assembly better than you. Overflowing your buffers is a mere keystroke away. Don't anger me, for you shall feel my rootkits.