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/.

Oh and I forgot to say one more thing:

>>1 you need to read SICP. Learning to build better abstractions and how to organize your code is how "code reuse" actually works.

I find myself reusing generalized libraries I wrote myself or other people wrote all the time. When you're solving a specific problem, the solution may be specific, but various things can be generalized and abstracted away into libraries which may be of use to you later, especially if the kind of problem you're trying to solve is similar to another one you already did. Of course, if what you're doing is completly novel, you're going to write a lot of new code.