h a l f b a k e r y
Reformatted to fit your screen.
add, search, annotate, link, view, overview, recent, by name, random
news, help, about, links, report a problem
or get an account
I'm responsible for long-term IT projects that require a good
bit of critical and creative thought. I'm also responsible for
maintenance, troubleshooting, and repair, often at a
moment's notice. To keep things from slipping through the
cracks, I just realized I can learn from the way hard drives
recovery from power failures and the like. A journaling file
system writes down what it's about to do, does it, and then
clears it off its list. If something breaks, it only has to look at
its log and the area where it was working.
I think I need to get a marker board for my desk.
||Congratulations, you've discovered the to-do list.
||It's different than a to-do list, though. This opens
up all sorts of tricks that computer use that
humans don't. Humans don't record EVERYTHING,
for example, and we don't because it would slow
us down. Journaling on a drive has a performance
penalty, too. Constantly switching our attention
from one thing to another is akin to the armature
seeking back and forth as it works its way
between the data and journal zones. How these
problems are resolved in ZFS, JFS, ext4, etc. can
be applicable to how humans get work done.
||Unless you have a more detailed idea here that you are leaving out, I second the MFD. Comparing some WKTE productivity techniques to a computer isn't exactly an idea.
||So, you're saying, do one thing at a time when you