docs(twitter): add 1737201090058219980 corpus (NOTimothyLottes logger + multi-session design)

3-post sibling to the 1736161886079533186 VK retrospective: same public-
domain release context, Dec 2023. Covers the mmap-ring-buffer error
logger and the multi-session rationale (crash auto-reload + log
preservation, no debugger).

docs/twitter/1737201090058219980/thread.md

@@ -0,0 +1,30 @@
+---
+title: "Multi-session is nice, since the binary auto reloads in some cases (crash, etc),"
+author: "NOTimothyLottes"
+handle: "@NOTimothyLottes"
+post_url: "https://x.com/NOTimothyLottes/status/1737201090058219980"
+post_id: "1737201090058219980"
+timestamp: "2023-12-19 19:59:50"
+post_count: 3
+reply_count: 0
+repost_count: 0
+like_count: 3
+view_count: 742
+---
+
+# @NOTimothyLottes — Multi-session is nice, since the binary auto reloads in some cases (crash, etc),
+
+## Post 1 (2023-12-19 19:51:05)
+
+Working towards a public-domain release of a cleaned version of my Win32 Vulkan NV+AMD compute graphics platform. What I used last for rapid prototyping (which is also IMO fine for releasable software). Won't call it an 'Engine' because it only provides tools to hang yourself ...
+
+## Post 2 (2023-12-19 19:56:49) — reply to Post 1
+
+Simplified the error logger today. Memory mapped file is definitely the way to go, one atomic per message, log multiple sessions, fixed size file acts like a message ring buffer. Background thread keeps the last message updating the same line on the console (for easy debug).
+
+![Media 1](./media/1737200333338595330_1.png)
+![Media 2](./media/1737200333338595330_2.png)
+
+## Post 3 (2023-12-19 19:59:50) — reply to Post 2
+
+Multi-session is nice, since the binary auto reloads in some cases (crash, etc), want to see why the reload happened, so don't want to clear the log. Yes, I still don't use debuggers, this logger + runtime shader recompile is all I use personally for dev work.