Added section on programming, added hotkey for explorer.

.obsidian/app.json

@@ -1,5 +1,6 @@
 {
   "legacyEditor": false,
   "livePreview": true,
-  "promptDelete": false
+  "promptDelete": false,
+  "vimMode": false
 }

.obsidian/hotkeys.json

@@ -7,5 +7,14 @@
       ],
       "key": "G"
     }
+  ],
+  "file-explorer:open": [
+    {
+      "modifiers": [
+        "Mod",
+        "Shift"
+      ],
+      "key": "E"
+    }
   ]
 }

.obsidian/workspace

@@ -7,8 +7,12 @@
         "id": "1f5b8eda0b2bb98d",
         "type": "leaf",
         "state": {
-          "type": "empty",
+          "type": "markdown",
-          "state": {}
+          "state": {
+            "file": "Programming/Random thoughts on programming.md",
+            "mode": "preview",
+            "source": false
+          }
         }
       }
     ],
@@ -65,6 +69,7 @@
             "state": {
               "type": "backlink",
               "state": {
+                "file": "Programming/Random thoughts on programming.md",
                 "collapseAll": false,
                 "extraContext": false,
                 "sortOrder": "alphabetical",
@@ -84,6 +89,7 @@
   },
   "active": "1f5b8eda0b2bb98d",
   "lastOpenFiles": [
+    "Programming/Random thoughts on programming.md",
     "Gaming/TTRPGs/D&D/AcqInc Team Y/Team Y.md",
     "People/Bonnie Wessler.md",
     "Gaming/TTRPGs/D&D/AcqInc Team Y/Zilara.md",
@@ -92,7 +98,6 @@
     "Gaming/TTRPGs/D&D/AcqInc Team Y/Guy.md",
     "Gaming/TTRPGs/D&D/AcqInc Team Y/Jorr.md",
     "Gaming/TTRPGs/D&D/AcqInc Team Y/Recap for 2022-04-17.md",
-    "People/Daniel O'Niel.md",
+    "People/Daniel O'Niel.md"
-    "People/Chad Banks.md"
   ]
 }

Programming/Random thoughts on programming.md

@@ -0,0 +1,4 @@
+## On tests: 
+#tdd #testing #worst_practices
+
+I read a quote that said "some tests are better than no tests", but it made me think that the inverse is also true in my experience. Some tests are worse than no tests. It seems easier to write bad tests than good tests, at least so far in my practice of writing tests after code. As I am delving into TDD, perhaps this will change. It seems even odds that it won't though.