Plain-text, Git-native knowledge
Why it stays
Important ideas should be searchable, diffable, portable, and legible to both people and future tooling.
Choose it again?
Yes. Durable formats outlive the application around them.
Uses
The workshop, not the storefront.
The systems and tool categories I rely on, why they earn a place, and whether I would make the same choice again.
Specific product recommendations will appear only after enough firsthand use to support a defensible opinion and disclosure.
Typed systems with explicit boundaries
Why it stays
Types, schemas, and boundary validation reduce ambiguity where data or authority moves between components.
Choose it again?
Yes. The upfront discipline pays back during every change.
A local AI infrastructure lab
Why it stays
Architecture decisions become more honest when they meet real compute, networks, failures, and observability.
Choose it again?
Yes. Small-scale operating experience exposes large-scale assumptions.
A source-controlled editorial workflow
Why it stays
Drafts, reviews, relationships, and publication decisions need provenance and a recoverable history.
Choose it again?
Yes. Publishing is an operational system, not a one-click action.
No affiliate links are present on this page. Future commercial relationships will be disclosed next to the relevant recommendation.