The Shared Folders

Monday, December 27, 2004

Tomorrow, dear reader, is not a day I am looking forward to.

Tomorrow, I’m going into the labyrinth alone. I’m heading into the shared folders.

The shared folders embody the essence of our company. They contain the past and the future - all inside of a single hierarchical structure.

A few months ago, I went into the folders, and they looked something like this:

I went to the powers that be, and asked for some insight as to the structure I found. Are the final specifications the complete specifications? Or are the complete specifications the final specifications? Do we make final specifications, then review, update, and mark them complete? Or do we make a complete set of specifications, then update, review, and mark them as final?

I suggested wikis, portals, or anything with WebDAV to make some sense of our artifacts, but the powers that be like folders. Shared folders. Shared folders with a deep hierarchy. The deeper the better.

The powers that be told me the folders would undergo a reorganization, and the latest version of specifications would be easier to find. Past versions would be put into an archive folder. “Great!”, I said. I returned to the shared folders a few weeks later to find this:

Looking at this, I feel like David Carradine’s character in the old Kung Fu series.

That is not a puzzle, Grasshopper. It is only something you do not yet know


Comments
haacked@gmail.com (Haacked) Monday, December 27, 2004
Dude, do the powers that be recommend using folder hierarchies for revision control of source code? I don't understand why they feel differently for documents. Especially specs which are arguably as important as the source code.
<br>
<br>Try getting them onto Sharepoint. You can have your folder hierarchies, but condense them a bit via version control.
Steven Campbell Monday, December 27, 2004
One of my clients has a similar folder fetish, except they also have some wierd document naming conventions that is too obscure to have any meaning. I feel your pain.
Scott Monday, December 27, 2004
Engineering tried to talk the powers that be into using source control, but we didn't get very far. Since engineering &quot;owns&quot; the source code, we do keep everything we possibly can inside SCM. If only everyone could see the power of a good SCM.
Comments are now closed.
by K. Scott Allen K.Scott Allen
My Pluralsight Courses
The Podcast!