Tinderbox Training Video - Daily Journal Time Tracking Project Management Part 1
|Tags||Tinderbox, aTbRef, 4Cs of Knowledge Exchange, Action Code, Export Code, Stamps, Separators, Incudes, Variable Cache, Agents, Daily Journal, Time Tracking, Project Management, Prototypes, Attributes, Plots, Timeline View, Hyperbolic View, Chart View, Attribute Browser, Treemap View, Crosstabs, Linking, Outline View, Map View|
|Example File||TBX - L Managing Daily-Journal-Time-Projects-FINAL30JAN21.zip (121.5 KB)|
|Revision||3, Jan 31, 2021|
|Related Lesson||Tinderbox Training Video - TBX - Deconstructing Daily Journal Date Descendants Management|
|Forum Post URL|
In this lesson, well, this is not exactly a lesson just yet, but it will be in future parts; I introduce you to my Tinderbox Daily Journal, Time Tracking, and Project Management Tinderbox file. I use this file, personally, every day to manage my work, play, and personal growth.
This file is a whale. It is a comprehensive integration of the vast majority of Tinderbox capability, as applied to daily journaling, time tracking, and project management. It includes, notes, agents, prototypes, attributes, action code, templates, export code, plots, separators, includes, cached variables, stamps, operators, every Tinderbox view, regex, back-references, designators, dot operators, performance optimization strategies, and so much more.
I’m putting this file out now so that everyone can use it, deconstruct it, ask questions, and give me feedback. In the coming weeks, I’ll record short videos focusing on not just how I implemented certain elements of this file but my intent behind the implementation and why I made the design decisions I did. Suffice it to say; this file went through significant rounds of incremental formalization.
Again, this is a big file, and it will be ever-evolving. I would love it if you help me refine it. I’d like to hear from you on,
- Any questions you have on the how to’s, the why’s, and the what’s
- What you don’t understand in this file
- Your thoughts on alternative approaches to optimize the action code, variable caching, prototype, etc.
- Catching “ghost code”
- Your logic and approaches for journaling, project, time and activity tracking
- Report formats
- File organization
- Ways to apply other Tinderbox capabilities to this file
- What your personal Tinderbox use cases are and how you’ll apply what you see here to them
- And anything else you’d like to discuss
Please reach out to me on the Tinderbox Forum or email me [firstname.lastname@example.org](mailto:email@example.com?subject=Tinderbox Training Questions and feedback). Also, please connect with me on LinkedIn.
* aTbRef: A Tinderbox Reference File