I like keeping a manual log (journal or diary) as I go.
Logs want to be a meta-file concept.
E.g. I only want to edit and view one log. I want to be able to track all of my work in a single place.
But, I also want to associate subsets of my overall log with particular projects.
E.g. I want to view log entries related to a project under ~/work/project/LOG. But I want to view these, and all others, under ~/LOG.
Editing this in ordinary files sucks. If I place it in a subdir/LOG I can't see it in ~/LOG, etc.
Suboptimal interactions with version control. I want version control for logs, but... Even if I am just working in projectdir/, editing projectdir/LOG, if I go off on a branch, edit projectdir/LOG, and switch back, I lose the log. The log wants to transcend branches.
I have occasionally tried to work around this by placing all of my log in the ciommit log. But that's not all that great an idea.
I wahnt as much automated log support, support for tracking personal history, as possible.
E.g. record the fact that I sent an email.
Automatically copy version control commit messages into my overall log. But, of course, make everything filterable/foldable.
Disclaimer
The content of this blog is my personal opinion only. Although I am an employee - currently of Nvidia, in the past of other companies such as Iagination Technologies, MIPS, Intellectual Ventures, Intel, AMD, Motorola, and Gould - I reveal this only so that the reader may account for any possible bias I may have towards my employer's products. The statements I make here in no way represent my employer's position, nor am I authorized to speak on behalf of my employer. In fact, this posting may not even represent my personal opinion, since occasionally I play devil's advocate.
See http://docs.google.com/View?id=dcxddbtr_23cg5thdfj for photo credits.
See http://docs.google.com/View?id=dcxddbtr_23cg5thdfj for photo credits.
Sunday, June 03, 2012
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment