I'm a progammer and am seeing if using TiddlyWiki might work well for documenting some of my projects. It seems so.
I have some SQL code that is a part of one task I'm doing. I wnated to spawn that code off into another document so that the main one was not cluttered with so much info that wasn't needed very often. So I used that excise feature to put the SQL code into another tiddler and I left a link to that in the main tiddler. I like it. The excised code i named "SQL to get Sample Records". Then it occurred to me that if I like this and add a bunch more projects, then that tiddler name is not all that specific, and will probably need to be improved. If I were in a file system, that sql code might be in its own folder so that such a simple name would be appropriate. So what do you guys do for TiddlyWiki? In a way, these Tiddler names make it so that everything is, in essence, in one folder. I guess I need to perhaps make the name more specific, with a prefix that resembles the name of the project or task. Instead of "SQL to get Sample Records" Maybe "Customer Design Change 2020 Feb - SQL to get Sample Records", though long and clumsy, is a tiddler name that will be better as more and more projects get documented in my TW. does that sounds like the best way to go? What are you guys doing in this kind of scenario? -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c1ef6458-7527-41b2-a9ae-e52b6d1c2913%40googlegroups.com.
