free roaming design patterns

I'm a self-taught programmer. I did not learn programming for the
purpose of making money, but for the joy of writing code, solving
problems and automating tasks. Thus, I belong in an entirely different
set of programmers, the lone wolves, those who never participated in a
project.

Differences go on: I wasn't involved with teaching institutions and
had adopted no teaching system. I studied only what made sense to me
at the time, programming languages, algorithms and data
structures, in a chaotic manner. The way I understand programming is
that I have a problem, and I need to find ways to automate it, or get
from point A to point B; how I'll do it is something that I figure out
naturally - I put no "meta" thought to it, as if it's obvious. As you
may have figured already, my coding style is chaotic as well; there's
little consistency to it, which is a kind thing to say, as others
would call it cryptic the least. In other words, my code is completely
personalized.

I never felt the need to study what is known as 'design pattern'. I
intrinsically know every design pattern there is on wikipedia (I was
curious enough to check). In fact, I may even not know it, but I will
certainly come up with it when the requirements are such.

Am I being elitist about it? Certainly. That's why the only programming
board I frequent is /prog/.

>>24
I've read some bits of SICP. I've quit mainly because of a loss of interest.
>>24
I've read some bits of SICP. I've quit because of a sudden loss of
interest. I'm quite familiar with abstractions and code
organization. It's just that everything in my code is personalized, ie
I can make sense of it while you probably need a lot of time and some
thought to it.

I don't do the 'code reuse' thing most of the times. I remember back
in 06 when I used to code in C I had implemented a <llist.c, llist.h>
that I'd use whenever I needed - I rarely do that anymore since the
languages I use are either terse or full of standard features (and
sometimes, in case of CL/Qi, both).

Do I write over and over again the same code that I've written so many
times before? I suppose that happens, unavoidably; I've solved many
problems and I've wrote much code over the years, enough to classify
as "experienced programmer without any experience".

I don't care for a v2; I don't want patches; I write my code in such
mindstate that dictates me to bulletproof everything, compute whatever
is to be computed and be done with it. If there might be a need for
features in the future, I'll implement a module system or script
language of the sort, but maintenance? Who cares!?! Plus, that's true
only for half the code I write; the other half is code I write to
research problems, code that is going to be used only by me and
whoever else finds the same problems interesting on the internet;
Yeah, I have the priviledge to be chaotic there.