Since nobody is reading this...

I believe that there is nobody out there who will find this, so I'll write semi-candidly.  I realize that this isn't really a journal, so I won't announce anything that I wouldn't say in conversation.

I'm working now at a company that provides online educational content with support for K-12 through graduate level courses.

Needless to say, it's rather more corporate than I've dealt with in a while.  Previous employers may have thought this a poor fit for me and my "style."  But, it's not.  I think I fit in quite well in this environment.  While I was a student I worked part-time for the university doing computer stuff and at that time I didn't fit in quite as well.  In hindsight I think that had more to do with the environment at that particular job than with an incompatibility between me and large-ish corporate culture.

In fact, I'm quite adept at functioning within the odd sub and meta-cultures that exist among corporations.  I learn systems quickly and I understand that the "way we do things" exists for reasons that must be investigated from the perspectives of nearly every person involved in order to understand them.  I also enjoy the process of learning to participate in these procedural actions.  It's almost like being a part of something larger and accomplishing more together than I could alone.

Currently I'm reviewing a process that was invented and maintained by my predecessor.  It takes course data which has had large portions of the formatting removed by the "export" process and attempts to guess at putting it back in.  As anyone reading this might guess; my current assumption is that this should be changed.  If format loss must be undone, why not simply change the process to not remove it in the first place.  Well, the answer in the past was that it was impossible.  However, that is one excuse I attempt to never use.

And so - I'm writing a full documentation novel on exactly what I feel should be modified about the current process.  And, as is typical for me, it far overshoots the mark on what would technically fix the problem.

And now I need to get back on it.