Devlog: On Process, Tools, and Stewardship

I want to say a quick thing about process, because a few questions keep coming up.

Some of my projects ship as text files. Some are developed in public. Some use AI as part of the creative process. All of this is intentional.

I work solo by choice. Not because collaboration is bad, but because I value continuity, creative control, and working within my actual means. I don’t have the budget for teams, and I don’t want to build projects around managing people rather than ideas.

AI, for me, isn’t a replacement for creativity — it’s a medium. Like a sketchbook that responds, or an instrument you tune and then listen to. It lets me iterate, explore, and refine without needing capital or permission.

I’m more interested in what grows than in performing a sanctioned process.

Text files and living documents are part of that. They allow transparency. They let you see the work while it’s becoming, not just after it’s been sealed and polished. That’s a feature, not a flaw.

I understand this isn’t everyone’s preference — and that’s okay. These projects aren’t trying to be everything for everyone. They’re experiments in stewardship under constraint: making honestly, with the tools available, and standing behind the results.

If you’re here for that kind of work, I’m glad you’re here.

If not, you’re always free to pass things by.

Thanks to everyone who’s been engaging thoughtfully and curiously — that’s what keeps this space worth tending.