My adventures rereading-the-pickaxe have reached the chapter on Ruby Fibers. Interesting stuff. Thought I would extrapolate from their initial example. My old static pages started from a MANIFEST file that looked something like this:
And so on. The path components create a topic hierarchy. There are only 89 files. This is not a lot to track, but it is enough that I can still be hazy about some high level details. For example, I have no idea how many pages are in each section.
Yes, this is just the example from the Pickaxe book with line.scan
changed to line.match
with a slightly altered regular expression.
This isn’t that helpful though. I already knew that the majority of my pages were in /geekery/
. Let’s adjust the regular expression so that the first two pieces of the entry count as a section.
Now I’m looking for possible subsections and lumping them with the top level section. Does this change get me more useful information (for varying definitions of useful)?
Yeah. It does. I can now see that the most of my static pages are about Parrot or Perl.
I recognize that all I’m doing in this example is shuffling complexity around. There’s nothing in the task that screams “OMG YOU NEED FIBERS TO DO THIS!” Still - I need to figure this stuff out somehow.
Anyways, back to work.
Backlinks
Added to vault 2024-01-15. Updated on 2024-02-02