spaghetti code

in computer programming, code which flagrantly violates the principles of structured, procedural programming. usually this means using lots of goto statements (or their equivalent in whatever language is being used) – hence the term, which suggests the tangled and arbitrary nature of the program flow.

spaghetti code is almost impossible to debug and maintain, and rarely works well.

programmers who write spaghetti code usually learned to code in an unstructured language such as basic, and never bothered to update their technical knowledge when they progressed to more serious languages.
you want me to debug this freaking spaghetti code? please tell me you’re kidding.
the product of when some ignorant, over-confident f-ckface writes in a hundred lines what you could write in a simple switch statement. this will undoubtedly include unneeded procedures and/or functions, unnecessary global variables, and unnecessarily abstracted include files. the purpose is to stroke the already inflated ego of said limp-d-ck programmer. and the result is that after management gets a clue and fires this jack-ss, you become the poor b-st-rd who has to debug this pile of sh-t when it inevitably breaks down.
security guard: what are you still doing here. it’s seven o’clock. shouldn’t you be at home with your wife?

poor b-st-rd: i’m still trying to figure out what the f-ck hank was trying to accomplish in this spaghetti code.
horrible, horrible, horrible code, but still (usually) fulfills it’s intended purpose. the english equivalent would be “i is go store buy vodka drink drunk sergawsdawq zzzzzz uuuugh talk loud”. it is completely screwed up in almost every way, but you still know it meant “i am going to the store. i will buy vodka. i will drink. i will get drunk. i will babble incessantly. i will p-ss out on the couch. i will wake up, go to work, and complain about my hangover.”
spaghetti code:
2351 goto main_sub3;
2352 preventraptor();
a coding style often executed by f-cktards unaware of or to lazy to use proper structural coding styles. the term refers to how the code becomes a hard to untangle m-ss, mutch like spaghetti. the intent of code is clearer if functions, breaking, cl-sses and loops are used, also you don’t have to go through loads of lines searching about and there is a nice tree structure and bunnys start jumping about and doing a happy dance. there is no excuse, therefore, for coding such a messy way, because if people continue to do this there will be lots of people on fire(and not in a good way, see s-xy lesbian orgy on fire).
holy moley look at that evil spaghetti code:

1 int r=0
2 print “moo”
3 r = r + 1
4 if r<10{ 5 goto 1 6 } 7 end i'll just clear it up and magically start using c instead of basic because basic sucks. 1 for{r=0;r<10;r++){ 2 printf("moo"); 3 } great, now i better get back to my s-xy lesbian orgy on fire.