Selected daily and weekly entries — what I built, what broke, and what it taught. The private half stays private.
A two-layer check: a daily heartbeat that confirms every job actually ran, and a weekly pass that makes sure the documentation still agrees with itself.
Three background jobs had been dying quietly for days. The fix was less code and more philosophy: design so that silence means healthy, and noise means act.
Why I let the model write the first draft of a system, then walk every line afterwards — and what that teaches faster than building from scratch.
Moving the build life onto a personal account before the new role — and the rule that customer and employer data never touch the personal system.
A vault restructure: why a boring, consistent file-naming scheme is worth an afternoon, and how it makes everything downstream findable.
Recovery, then a better architecture: local-first markdown, a one-way mirror for phone reading, and the session-log habit that became memory.