I am writing to you in hopes that this will generate some momentum to force you
to step down as president. I actually considered voting for you at one point
during your campaign. Your promise to clean out the Washington establishment...
I've been using Things and now
Asana for task management for over a year now. What is
great about these tools is I can set due dates for all my tasks and they
magically appear on that day to remind me to do that. I rely on the today
view both these tools have to tell me what needs to be done that day as well
as the upcoming task view to tell me what the next few days are like.
However, I found that I wasn't being careful about when I was scheduling
tasks. Because of that I was over-scheduling my days. I would load up the
upcoming days with a set of tasks that I couldn't possibly finish. This was
especially true for the weekends where I'd arbitrarily schedule personal tasks
for the weekend and come Saturday find I had 17 things to do.
What, sadly, took me a long time to realize was that no matter how much
technological support I have to get tasks done, task-management isn't just
enumerating everything you need to get done and then doing them.
I still need to carefully plan when I'm going to get stuff done.
I feel that it's very important that any code I write for my research is
available online so that anyone can access and read it. I also want people to
be able to view all the individual changesets that went into the software.
That way they can see the full thought-process that went into a project. That
is why, for example, Tuner is on GitHub.
However, when I am developing a feature for a paper, I don't want the code to
be public until after the paper is accepted. Furthermore, I want to keep my
private changes online so that I can share them with collaborators. So what
to do? What I do is have 2 git repos online, a public one and a private one.
Then, I use feature branches in the style of
git-flow to keep
track of all my changes. I keep them in my private repo until I'm ready to
expose them to the world and then move them to my public repo once I'm done.
I detail my specific setup below.
With the new website I wanted 2 sources of posts, regular blog posts and
projects. This boils down to having 2 separate index pages, one for my blog
posts and one for my projects. The issue with jekyll/Octopress is that all
valid files in any _posts
I have a terrible memory for what I've done in the past. I can barely
remember what I had for breakfast let alone specifics about a data analysis I
did from the past week. I tend to go down so many wrong paths that by the
time my weekly supervisor...