Face Down, Ass Up That's the Way We Like to... Code?

Well, at least I do.

I'm nearly through the phrase of a project's life cycle where we take all the documentation of what we're supposed to do (Detailed Requirements Specification or DRS) and create a technical explanation of how we plan on doing it (Technical Design Specification or TDS).

To me, this is the most boring part of the project. I do a bunch of research then determine how much 'splaining I can do without actually doing any coding. A reasonable amount of explanation is necessary so that the higher-ups don't ask "are fuggin' crazy? how are you ever gonna make that work?" However, to much makes you feel like you're swimming in peanut butter-- it's just kinda drudgery.

However, now I'm floating into the coding/implementation phase where I actually get to code-- the Crue rocks, gnats bother folks and coders code. It's part of the natural order of things.

And when I code I like to get into Flow. A guy named Csikszentmihalyi wrote a few books explaining the concept of flow, or optimal performance. It's that thing you get into where you lose track of time and before you realize it you've expertly assembled 1,0000 widgets and now it's quitting time.

So I like to go heads down, don't mess around with too much other shat, lock on the Bose headphones (making sure enough super glue is in place to hold them together) and just start a tear.

Flow-- it's not just the thing under your feet.