View Single Post
  #3  
Old 09-25-2009, 04:07 AM
armsys armsys is online now
Registered User
 
Join Date: 12-19-2007
Posts: 647
Re: Re: Source Code Archive

Quote:
Originally posted by zargron
Yes & no. I have been through the pandora of "thorough source documentation" and come out the other side a little battered and bruised. Overall i found the reward too meager for such efforts. I focus on "software management", using UR of course. I create a separate UR database for each software topic (eg. application, suite of related applications). I create main branches for things like:
* Ideas
* Documentation
* Publishing
* Strategy
* Design

Each "software" database becomes my main repository for material associated with a specific application. If i fix a (simple) bug, i might not update the database. If i do an enhancement, i update design, documentation and so forth before/during/after the modifications. I focus on concepts and modularity in the repository, allowing comments in source code to handle documentation of granular aspects. BTW: I manage the work load (projects / TTD) for all applications in my "core" PIM database.

Wouldn't it be wicked if there was an easy way to have syntax highlighting within UR? Then perhaps i would delve into the possibility of linking my UR database to source code files. (I use the "Folder" item to document and point to locations of source files and program resources.)
For documentation, I develop my own Access database to keep tracks all sort of documents, including URDs of course. As far as I'm concerned, for documentation, it requires highly structured database. In fact, in my case, nearly all things are prioritized, including authors, publishers, document types,....etc. As a result, I can always re-prioritize. In this case, UR may not be helpful.

But for source code, it's highly plausible. It's impossible for me to memorize all objects, RegEx expressions, SQL statements,...etc.

Armstrong
Reply With Quote