Re^2: LAMP and hosting: Convenient Perl solution, similar to PHP setup?

re "keep a diary"

I'd call that revision control. On the other hand, browsing around revision history and commit messages isn't nearly as easy as a file that you made specifically to record discoveries, even if it is likely far more detailed and accurate.

Comment on Re^2: LAMP and hosting: Convenient Perl solution, similar to PHP setup?

Replies are listed 'Best First'.
Re^3: LAMP and hosting: Convenient Perl solution, similar to PHP setup? by locked_user sundialsvc4 (Abbot) on Mar 14, 2008 at 15:00 UTC
Project management systems can have “diary” capabilities, and if they exist they should be used. But a revision control system can only hold ... a revision. And by the time a “revision” has been created and checked-in... well, by then it's just too late. You “gone and done it.”
Re^4: LAMP and hosting: Convenient Perl solution, similar to PHP setup? by kyle (Abbot) on Mar 15, 2008 at 01:50 UTC
The "diary" of revision control is the commit messages. Even crusty old RCS featured this. I agree that a tool dedicated to this kind of work is better than what you get from revision control. I say that not having used them, but I have no problem believing there could be a better diary than what you get free with your revision control. You “gone and done it.” Sort of. The beauty of revision control is that you can then go and undo it. I find it useful to commit early and often, at just about anything that's a logical unit of change. It's just as easy to back out ten revisions as it is to back out one.	[reply]