Notes
Notes from inside the work.
A public notebook for product decisions, systems, AI, data, markets and the trade-offs that only become visible when something has to ship.
Latest note
Move fast, but know what you are measuring
A Dublin Tech Summit field note on one-page plans, uncomfortable metrics, founder-led market learning, and why more motion is not the same as progress.
The archive
Open questions, decisions and lessons.
Not a diary. Each note starts with something real, extracts a pattern and leaves a useful next move.
Notes
Background agents and the work humans still need to own
Why useful background agents need triggers, queues, reviewable outputs, and clear human ownership more than they need vague autonomy.
Read note →Notes
Agent Skills are AI workflows
Why agents need process, training material, and verification steps before their work becomes predictable enough to trust.
Read note →Notes
Growth analytics should create decisions, not dashboards
How I think about connecting Search Console, PostHog, and Hermes into a weekly review loop for acquisition, product behavior, and follow-up work.
Read note →Notes
The underrated part of AI agents is cron
Why scheduled AI workflows matter when the goal is steady, reviewable work instead of impressive one-off demos.
Read note →Notes
Building MCP: when your data becomes part of the agent workflow
A practical note on why MCP matters when agents need real data, bounded tools, auditability, and human judgment instead of another pasted prompt.
Read note →Notes
How I use Obsidian as operating memory
A practical look at how my Obsidian vault, cron jobs, GitHub issues, and Hermes workflows keep context moving toward decisions and reviewable work.
Read note →Notes
Hermes, my agent for everything
How I am using Hermes as a practical execution surface across notes, repos, GitHub Projects, cron workers, QA, and publishing without handing over judgment.
Read note →Founder/operator note
Mentorship Is an Operating System
A personal note on why junior developers need structure, patience and real feedback, not motivational speeches.
Read note →Founder/operator note
Good Teams Make Product Work Possible
A short note on the habits that make technical teams useful: ownership, responsibility, autonomy and closeness to the customer problem.
Read note →