(Don't) take the Boidem, for example.
Over the years I've learned to map out the various parts of a web site in such
a way that I'm able to readily work with the parts without getting lost within the whole. But that's not the case with the
Boidem. Eleven and a half years ago, when I started building the Boidem, I had
close to no experience with HTML or with building web sites, and, having no idea
that it would flourish into a couple thousand pages, saw no particular need to
plan ahead. Had I done so, I might have thought that it would make sense to perhaps
put each year into a separate sub-folder, or perhaps store the
images in a separate folder. It took me about a year and a half until I realized
that a logical naming system for the various pages of the Boidem would make life
easier for me (and keep me from inadvertently deleting pages by saving new files with the same name).
Perhaps there was also something in the hypertextual nature of the Boidem as seen
from the outside that caused me to want to maintain a bit of a mess, a sort of
primordial soup, on the inside as well. I'm really not sure.
Go to: For me, of course, or
Go to: One tool to rule them all?