Stoyan

Indie dev building: Continuum, SubKeep, GitGlow, and small game experiments. Sharing what ships, changes, and still needs testing.

[Stoyan @StoyanBuilds]

The stubborn universal build belongs to GitGlow: https://t.co/LDUE5HIB6q

[Stoyan @StoyanBuilds]

One argument in the wrong place made GitGlow reject a perfectly universal macOS build. Tiny bug, loud consequence. Release scripts don’t need glamour; they need suspicion and receipts. #buildinpublic

[Stoyan @StoyanBuilds]

@naiivememe time to buy that dip 🍽️

[Stoyan @StoyanBuilds]

@anshuc This is the kind of wisdom I was hoping to find in this scrolling session 🙌 😂

[Stoyan @StoyanBuilds]

@matthias_mrc scrolling X of course 🤣

[Stoyan @StoyanBuilds]

@victor_bigfield I share exactly the same pain and forced myself to focus on release, stabilize, and market market market everything I built so far and then eventually move on to something new 😂

[Stoyan @StoyanBuilds]

This release-workspace work is in GitGlow: https://t.co/LDUE5HIB6q

[Stoyan @StoyanBuilds]

A clean worktree can still tell the wrong story when the merge evidence is stale. I tightened GitGlow’s workspace reporting because “clean” is a filesystem fact, not proof that the job is done. #buildinpublic

[Stoyan @StoyanBuilds]

A small but important Canvas constraint: staged images are local image data, not remote URLs fetched in the background.

They enter the local asset store only after the proposal is approved.

[Stoyan @StoyanBuilds]

@muhammadhamid_2 I just didn't have the time to deal with the tiriad of emails from their compliance team, and just resorted back to Stripe. I'm wondering if this was an onboarding one-off situation on their end, or this is their usual practice. To bore their potential customers to death 🤣

[Stoyan @StoyanBuilds]

Moving SubKeep from Lemon Squeezy to Stripe looked like a payments task. The real work was keeping existing access intact and the rollout reversible. A checkout is easy; trust is the migration. #buildinpublic

[Stoyan @StoyanBuilds]

The new Indie Log workspace is part of GitGlow: https://t.co/LDUE5HIB6q

[Stoyan @StoyanBuilds]

AI can draft an Indie Log entry quickly. The useful part is refusing stale or interrupted runs before they become history. GitGlow now treats “almost finished” as exactly that—not publishable truth. #buildinpublic

[Stoyan @StoyanBuilds]

SubKeep adds folders and focused workflows to Google Keep: https://t.co/cNF7QyNLzc

[Stoyan @StoyanBuilds]

Automated checks and human activity shared one feed in my marketing tool. Convenient—until green checks started looking like decisions nobody made. Provenance is a product feature, not audit garnish. #buildinpublic

[Stoyan @StoyanBuilds]

Already possible in the brand new Canvas experience in Continuum, feel it for yourself :))
https://t.co/0Ji2VR3wKh

[Stoyan @StoyanBuilds]

AI is often asked to “organize the board.”
That is too vague.

A better job: name the audience, let it propose a reading order, and show the proposed moves before the board changes.

[Stoyan @StoyanBuilds]

The Agent Observatory lives inside GitGlow, my local-first view of repository work: https://t.co/LDUE5HIB6q

[Stoyan @StoyanBuilds]

Most agent dashboards are good at looking alive. I wanted one that stays useful after the motion stops, so GitGlow now records enough context to replay a run. Observability should survive the demo. #buildinpublic

[Stoyan @StoyanBuilds]

“It runs on my machine” got upgraded this week to “it can recover on my machine.” Password resets, backups and restores did more for my confidence than the deployment ever did. Reliability begins after the demo. #buildinpublic