What this journal is for.

The /blog has a clear job: essays about why I built Arden a particular way. Comparison pages. Explainers about how the CSV importer handles a Chase statement. Product-shaped pieces — the kind of thing someone Googling “private budgeting app” or “Mint replacement without Plaid” might land on and find useful.

The /journal is the other half.

Building a finance app as one person is strange. I'm active-duty military, working in networking and cybersecurity. I work on Arden on evenings and weekends. Eventually I'll leave the service and go full-time on it — until then, every feature ships around the seams of the day job. The marketing site says Independently built. No investors. No data sold.That's true. It doesn't tell you what that actually looks like.

This is where I write about the experience of it.

What I'll write here

• Why I’m doing it this way instead of taking VC money.
• What it’s like to ship Arden around a military day job.
• Mistakes I’ve made and what I’d do differently.
• Decisions I haven’t made yet, and how I’m thinking about them.
• Honest assessments of what’s working and what isn’t.

What I won't write here

• Financial advice. I’m an engineer with a privacy obsession, not a CFP. The "should you do X with your money" content stays out — that bar belongs to people with credentials.
• Anything detached from my actual situation. If a piece sounds like generic indie-founder content, it doesn’t belong here.

Cadence

One essay a month, give or take. Slow enough that I have something worth saying.

If you want product philosophy, head to /blog. If you want to read about the person behind it, you're in the right place.

— Tyler