youthlib dev

i would also add...

[1. read emails]
[2. post to planet sven or personal blog]
3. Respond to emails
4. Write new posts to Notepad
5. Respond to comments on Notepad
6. Write new material for Generator

the theory is that reading the email as the first thing gives you an idea of what needs to be addressed, but you don't have to address it right away. i think it's important to ground yourself in the "ham & cheese" blog with that stuff in the back of your head, and then plunge into the youth lib stuff, which begins with responding to emails. because once you start, you won't stop and then you'll never find the time for planet sven. (i think planet sven is a nice place to maintain your personal voice, rather than your concentrated youthlib voice.) take time for you! :)

but if the goal is to focus foremost on connections w/ others, then perhaps a reshuffling of notepad priorites would be in order, so thus:

[1. read emails]
[2. post to planet sven or personal blog]
3. Respond to emails
[4. Respond to comments on Notepad]
[5. Write new posts to Notepad]
6. Write new material for Generator

and as long i'm beating this into submission, i'd like to add another step: checking the development site! :D

1. read emails
2. post to planet sven or personal blog
3. Respond to emails
4. review dev.youthlib
5. respond to dev.youthlib if needed
4. Respond to comments on Notepad
5. Write new posts to Notepad
6. Write new material for Generator