@@ -263,3 +263,44 @@ years ago happens to be. So I'm giving it a shot. I can see the wisdom in taking
263
263
frequent breaks for those kinds of tasks, and hey, worst case I just uninstall
264
264
the app and still have some amount of work done. Seems worth a try.
265
265
266
+ ... Briefly popping back to say: ` git ` commits can be a time saver! I was
267
+ wondering how much work I had actually ported from my notebooks. And all I had
268
+ to do, thanks to how I structure commit messages, was ask ` git ` :
269
+
270
+ ```
271
+ $ git log --grep='ch06'
272
+ commit a0104646e9effd495303584a02e134c8e323a43f
273
+ Author: Thomas E. Hansen <...>
274
+ Date: Thu Jun 6 14:09:13 2024 +0100
275
+
276
+ [ ch06 ] Rename to what it actually will be about
277
+
278
+ commit a9be52442b2f953f4c24e0a451f0046f78dd6b2f (origin/main, cs/main)
279
+ Author: Thomas E. Hansen <...>
280
+ Date: Wed Apr 3 19:04:19 2024 +0100
281
+
282
+ [ ch06 ] Start writing up dsa-gen:edges
283
+
284
+ There is _a lot_ to detail in terms of edges; turns out (as I
285
+ increasingly recall) that stuff was really complicated actually! Nice!
286
+
287
+ commit a0e7af7072e451cb18f8c8f6da485080a4d1608a
288
+ Author: Thomas E. Hansen <...>
289
+ Date: Wed Apr 3 18:04:29 2024 +0100
290
+
291
+ [ ch06 ] Port dsa-gen overview from blue notebook
292
+
293
+ commit a0846ba7a782c1701269f62819a95a1b7d4f0273
294
+ Author: Thomas E. Hansen <...>
295
+ Date: Mon Apr 1 17:14:42 2024 +0100
296
+
297
+ [ ch06 ] Reconstruct mental map of blue nb
298
+
299
+ Not a huge wordcount increase (might even be a decrease), but this was
300
+ massively helpful in terms of remembering how things went and figuring
301
+ out where they were written down.
302
+ ```
303
+
304
+ Now I know where to resume my work, avoiding wasting time copying stuff from my
305
+ notebooks that was already there!
306
+
0 commit comments