X-Git-Url: https://feistymeow.org/gitweb/?a=blobdiff_plain;f=scripts%2Fnotes%2Finfo_overload_report.sh;h=05fee6f30eb7370d82ba9175310187a5a2a4853a;hb=7cb361cd12aea2938534e7d4166ba2139ab4d382;hp=2683ed7d2be982a8c91e2cc87f54667c1570af16;hpb=71303a6ccf382269d70249e7ab5a6bdc080bdca1;p=feisty_meow.git diff --git a/scripts/notes/info_overload_report.sh b/scripts/notes/info_overload_report.sh index 2683ed7d..05fee6f3 100644 --- a/scripts/notes/info_overload_report.sh +++ b/scripts/notes/info_overload_report.sh @@ -1,7 +1,7 @@ # these metrics are how bogged down we are in to-do type items. -REPORT_FILE="$HOME/cloud/overload_history.txt" +REPORT_FILE="$HOME/cloud/fred_stats/overload_history.txt" # given a path, this will find how many items are under it, ignoring svn and git files, plus # other patterns we happen to notice are not useful. @@ -98,6 +98,8 @@ full_report+="count\tcomplexity\tweight (kb)\tcategory\n\ ================================================================\n\ " +analyze_hierarchy_and_report ~/cloud/urgent "high priority" + # notes are individual files of tasks, usually, although some are combined. analyze_hierarchy_and_report ~/cloud/grunty_notes "grunty notes" @@ -108,21 +110,24 @@ analyze_hierarchy_and_report ~/cloud/feisty_notes "feisty meow notes" analyze_hierarchy_and_report ~/cloud/branch_road "hearth and home notes" # scan all the items declared as active projects. -analyze_by_dir_patterns "active items" ~/cloud/*active* +analyze_by_dir_patterns "active items" ~/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 "project files" ~/cloud/project* ~/cloud/research* + +# snag any work related items for that category. +analyze_by_dir_patterns "job and work tasks" ~/cloud/job* # scan all the trivial project folders. -analyze_by_dir_patterns "trivial items" ~/cloud/*trivia* +analyze_by_dir_patterns "trivial items" ~/cloud/trivia* -# source examples need to be sucked into other places, other codebases. they are not -# supposed to pile up here. -analyze_hierarchy_and_report ~/cloud/example_source "source examples" +# 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" # 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. -analyze_hierarchy_and_report ~/cloud/unsorted "unsorted files" +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.