magic alias fix

[feisty_meow.git] / scripts / database / info_overload_report.sh

diff --git a/scripts/database/info_overload_report.sh b/scripts/database/info_overload_report.sh
index 3809113815856a698ff6ea55441d83543c6907b2..8b1ef49861dee175b8e2e3983e650ab4071cfdc7 100644 (file)
--- a/scripts/database/info_overload_report.sh
+++ b/scripts/database/info_overload_report.sh
@@ -98,23 +98,29 @@ full_report+="count\tcomplexity\tweight (kb)\tcategory\n\
 ================================================================\n\
 "
 
-analyze_hierarchy_and_report ~/cloud/urgent "high priority"
+analyze_hierarchy_and_report ~/cloud/urgent "high priority (aieeee!)"
 
 # notes are individual files of tasks, usually, although some are combined.
-analyze_hierarchy_and_report ~/cloud/grunty_notes "grunty notes (external facing things?)"
+analyze_hierarchy_and_report ~/cloud/grunty_notes "grunty notes (externalities)"
 
 # feisty notes are about feisty meow(r) concerns ltd codebase development.
-analyze_hierarchy_and_report ~/cloud/feisty_notes "feisty meow notes (code related)"
+analyze_hierarchy_and_report ~/cloud/feisty_notes "feisty meow notes (mondo coding)"
 
 # home notes are a new top-level category; used to be under the grunty.
-analyze_hierarchy_and_report ~/cloud/branch_road "hearth and home notes (branch road, yo!)"
+analyze_hierarchy_and_report ~/cloud/branch_road "hearth and home notes (branch road)"
 
-# games and fun stuff.  not sure why these count as backlog, but whatever.
-analyze_hierarchy_and_report ~/cloud/games_yo "games, yo!"
+##
+#yeah, games don't count as technical debt or backlog.  that's nonsense.
+#  the whole point of playing games is as a way to let off steam or escape from current
+#  real world unpleasantness, so tying the game stuff into my huge lumbering backlog is
+#  like saying lets inject toxins in our brain.  screw that.
+##
+## games and fun stuff.  not sure why these count as backlog, but whatever.
+#analyze_hierarchy_and_report ~/cloud/gaming "games yo"
 
 # some source code that needs to be sucked into other places, other codebases.  they are not
 # supposed to pile up here.  but they have, so we track them.
-analyze_hierarchy_and_report ~/cloud/scavenging_source "source scavenging"
+#analyze_hierarchy_and_report ~/cloud/scavenging_source "source scavenging"
 
 # and then count up the things that we think will be cleaned soon, but one thing we have learned
 # unsorted files haven't been categorized yet.
@@ -122,19 +128,19 @@ analyze_hierarchy_and_report ~/cloud/disordered "unsorted files"
 
 # we now consider the backlog of things to read to be a relevant fact.  this is going to hose
 # up our weight accounting considerably.
-analyze_hierarchy_and_report ~/cloud/reading "reading list"
+analyze_hierarchy_and_report ~/cloud/reading "reading list (for a quiet afternoon)"
 
 # scan all the items declared as active projects.
-analyze_by_dir_patterns "active items" ~/cloud/active*
+analyze_by_dir_patterns "active issues" ~/cloud/active*
 
 # scan across all appropriately named project or research folders that live in the "cloud".
-analyze_by_dir_patterns "project files" ~/cloud/project* ~/cloud/research*
+analyze_by_dir_patterns "running projects" ~/cloud/project* ~/cloud/research*
 
 # snag any work related items for that category.
-analyze_by_dir_patterns "job and work tasks" ~/cloud/job* 
+analyze_by_dir_patterns "jobby work tasks" ~/cloud/job* 
 
 # scan all the trivial project folders.
-analyze_by_dir_patterns "trivial items" ~/cloud/trivia*
+analyze_by_dir_patterns "trivialities" ~/cloud/trivia*
 
 full_report+="================================================================\n\
 "