...but formalizing it isn't.

Monday's class this term is Software Applications/Programming. It's basically a beginner-level software engineering class: specification, design, programming, testing, and implementing an application. Sounds easy enough, right?

Okay... no, it doesn't sound easy... because it really isn't. I've been writing short stories for years; after a lot of practice, it's nearly second nature: have idea, start writing, finish writing, show off cool story (boy, my ego... going to have to have it shrunk again... ;) ).

What's missing from this sequence? Planning. Short stories are spontaneous.

Software isn't.

First, you have to have the idea. Simple enough.

Now, you have to specify what it can and can't do. This is a pretty formal declaration of the limits and constraints of your idea... basically, "When is it done?" Which is a lot easier said than done.

Next, you have to present the idea. I don't really like standing in front of people and talking. Face-to-face with one or two people is fine; more than that, and I feel the need to find a corner and hide.

Then you get to think about the classes within the application, what tools to use (Java? C++? VB? FORTRAN?... ok, not FORTRAN... I have no idea how it works), and how much time you feel you can spend on it.

Now, you can type the code. (The "easy" part. Right? :p )

Which makes me wonder...

What the **** have I gotten myself into?

Add all this work to the other two classes (I can almost sleep-walk through Group Dynamics; Introductory Calculus, not so much), and I have a feeling my blogs are going to get spaced apart a little more than they have (so have patience, tekmet: no need to poke me... :) ). So, if I tend to disappear every now and again, you have a good idea why.

Of course, it could be worse... I could become this poor guy.