Self discovery of your developer personality

I've seen various posts 'round here about the kind of developer personality you have. I've done some thinking, and I think by some people's standards, mine is not great.

In the current job that I'm on, there is more organization than any other project I've ever been on. In fact, there are more meetings about how to organize the organization than I've ever seen. (This is night and day from my last gig, where there wasn't even any real documentation.)

It drives me kind of crazy. One component, the first in this huge project, does some simple data calculations. It was budgeted to have 60 hours for design. I prototyped it in a couple dozen lines of code in about two hours. The reaction to me doing this ranges from, “Good thinking,” to, “What the hell are you doing? Where are your design documents?”

Just as I believe that clear separation of various application layers is not a clear, concrete concept for all scenarios, I don't think that planning to death is the only way to do things either. You get to a point where the design and break down of various tasks is so focused and specific, per the requirements, that you don't need to document design at that point. Instead, and especially in our case using C#, you can derive design documentation from your little prototyped classes.

The result is that I come off as the demon in both extremes. In my last one, people hated my need for documentation, and in this one, people hate me for saying their extreme organizational process is overkill.

I need to find my place in the world with the 75% of people who aren't guerrilla coders or mega-enterprise architects so I can keep my sanity.