What you will find here
- Tape
- workflow design
- practical automation
- small operational improvements
Journal
Practical writing for clearer systems, better workflows, and calmer delivery.
The journal is where guides, working notes, and small patterns live. If a piece helps someone use a system better, understand a workflow faster, or avoid a repeated mistake, it belongs here.
Featured entry
article Tape 13 Jun 2026 3 min read
Introducing Obsidian Pulse
An audit trail, rollback, and deleted record recovery tool for Tape organisations — built after the question "can we get that record back?" came up one too many times.
Read entry →Archive
More notes, guides, and working examples.
guideTape
Building a clearer record title in Tape
Use a calculation field to turn status, reference context, and a name into one readable title that stays useful across related records and lists.
13 Sept 20255 min read
Read entry →guideTape
Generating a reference number in Tape
A practical guide to creating reference numbers in Tape, from the built-in unique ID field to custom date-based formats.
13 Sept 20256 min read
Read entry →guideTape
Building date records in Tape
A practical pattern for generating related year, month, and day records in Tape using automation and batch creation.
14 Sept 20259 min read
Read entry →guideTape
Handling potentially empty fields in Tape
A practical way to build calculation fields that still read cleanly when some source values are missing.
14 Sept 20255 min read
Read entry →articleProductivity
Automating string encoding with Alfred
A lightweight Alfred workflow for URL and Base64 encoding that keeps common text transformations quick and close to the work.
13 Sept 20254 min read
Read entry →articleProductivity
UUID and key generation with Alfred
A quick Alfred workflow for generating UUIDs plus hex or Base64 keys without dropping out of the task you are already in.
13 Sept 20256 min read
Read entry →Want writing that starts from a real workflow problem?
The journal is one place where practical patterns live. If you are dealing with a brittle system or a workflow that has grown messy, the stronger next step is usually to look at the operating problem directly.