JOURNAL / FIELD NOTES
Build logs, product notes, and community conversations about software that keeps a person in the loop.
Patient-owned records should be exportable without handing a third party a permanent view of the account. This build uses a local Chrome/Puppeteer harness, keeps credentials in the user's browser, and treats every export as a visible, reviewable step.
The hard part was not downloading a file. It was drawing a clean boundary around sensitive data, recovery, and what the tool can safely claim.
Perks Reminder started as a small answer to a recurring problem: benefits expire quietly, and the data needed to remember them should not require a bank login. The product keeps reminders, evidence, and correction paths close to the person using it.
The strongest product decisions were small ones: exportable data, duplicate-card workflows, and a visible distinction between a reminder and a financial recommendation.
Putting a privacy-first export tool in front of a technical audience sharpened the message: local control is a product feature, but only when the recovery path and the limits are clear too.
The conversation became another evaluation loop: explain the boundary, listen for the failure mode, then make the next build easier to inspect.
DAILY / AI BUILDER BRIEF
Daily field notes on the AI developments that change what builders make, use, and prepare for.