How I Think About Naming Projects and Domains
A reflection on how naming projects and domains shapes structure, scope, and long-term coherence, and why naming has become a core part of building systems.
Systems Thinking17
Check out the latest posts
From Blogs to Systems: Why I Stopped Thinking in Websites
A reflection on moving beyond website-first thinking toward interconnected systems, and why infrastructure, continuity, and structural relationships now shape how I build and organize long-term work.
Why I Version Datasets Like Software
A reflective article on why public datasets are versioned like software, and how change management, continuity, and structure shape long-term open knowledge projects.
What I Learned Publishing My First Public Dataset
A reflective article on publishing a first public dataset, including lessons about structure, documentation, reusability, and the role of open knowledge infrastructure.
Why I Keep Some Projects Separate (and Merge Others)
A reflective look at how and why some projects remain separate while others are merged, exploring structure, clarity, and long-term system design.
How to Evaluate a Blog Post: A Systems-Based Framework
A systems-based framework for evaluating blog posts. Learn how to assess clarity, structure, and depth to create stronger, more durable content.
AI as Infrastructure: What We Lose When It Disappears
AI is becoming infrastructure. This analysis explores what systems lose when AI disappears, including hidden dependencies, coordination gaps, and shifting skill structures.
Open Knowledge as a Strategy, Not a Philosophy
A reflective look at open knowledge as a strategic decision, exploring how publishing, structure, and reusability shape long-term systems and projects.
Designing a System for Solo Travelers
An exploration of why solo travel resources should move beyond articles toward structured systems built on tools, data, and interconnected information.
What I Learned Building 400+ Repositories
A reflection on building 400+ repositories, focusing on patterns, mistakes, and what actually scales in long-term systems and open knowledge projects.
Why Open Source Projects Need Standards, Not Just Code
Why sustainable open source projects need standards beyond code, including documentation, governance, trust, and long-term maintainability.
The Tradeoff Between Breadth and Depth in Curated Resources
An analysis of the tradeoff between breadth and depth in curated resources, explaining how incentives, scale, and purpose shape their structure and long-term usefulness.