I am a product and program person who also likes to build. That pairing shows up often in profiles; what I have come to value in my own story is something quieter: artifacts people can click.

Listing “AI” is easy. Walking someone through a live system—what it does, what tradeoffs it makes, and the week a deploy taught you something new—is a different kind of introduction.

So I have started treating side projects less like private sketches and more like small beacons: not loud growth hacking, just a steady way to say, “If you are curious how I work, here is something you can explore on your own time.”

A small stack I hope is easy to discover

When someone is deciding whether to collaborate—hiring, partnering, inviting a talk—they are often asking a gentle question: does this person follow through, and do they mean it?

I cannot answer that for them. I can leave breadcrumbs that feel honest:

  1. A live product with a URL. My daily financial report is not a slide deck. It is a pipeline: ingestion, scoring, narrative passes, HTML generation, CI, GitHub Pages. People can disagree with the model—that is healthy—and still see how the pieces connect.

  2. Writing that lingers on reasoning. This blog is where I try to slow down enough to show tradeoffs, mistakes, and constraints, not only the parts that worked on the first try.

  3. A public knowledge base when someone wants depth. AI Assisted Work is the “syllabus” layer: onboarding paths, notes on context engineering, and references for readers who want to go past a single article.

None of that replaces a real conversation. It can shorten the warm-up—so an email can start past “do you actually build things?” and closer to “here is the problem I care about.”

Light positioning, heavy sincerity

Formal marketing playbooks still make sense when you are shipping a SKU to a known buyer. For an individual builder–PM path, I keep a softer map:

  • People I have in mind first: hiring managers and partners who care about judgment and craft—who want evidence, not only adjectives.
  • People I have in mind second: practitioners who might borrow a workflow—how I use Cursor, how I frame risk, how I collaborate with agents without handing over the steering wheel.
  • Language I try to use: ship dates, public repos, live pages, and candid “what is still rough” notes. I trust credibility more when it sits next to the blemishes.

The thread I want is not “I am the best at everything.” It is closer to: here is a body of work; here is what I would tighten next if this had a dedicated team.

How AI shifts the math (for me)

Tools like Cursor do not replace taste. They can lower the friction between an idea and something URL-shaped. That matters for this little public stack because each modest release adds context:

  • A weekend sketch can grow into something with tests and CI guardrails.
  • A draft post can be argued with line by line—then still my choice what ships.

The win I notice is not “I used AI” (many people will, and that is fine). It is cadence with care: a few more finished artifacts per season, all pointing at the same through-line—end-to-end systems I can explain.

What I am skipping on purpose (for now)

  • Paid ads that push strangers into a funnel. Maybe someday; it is not the center of how I want to show up today.
  • Metrics I cannot stand behind. I would rather offer a link, a commit history, or a risk score that updates when the world does.

If you want to experiment without a “rebrand”

You do not need a huge content plan on day one. One artifact you would happily put in the first line of an email—something a stranger can open and understand in a couple of minutes—is a generous start. Write the short README or launch note, live with it for a month, then decide what deserves a sibling.

If you already ship mostly in private, you might ask whether the next iteration could be public by default. That habit, taken slowly, can move the story from “I tell you what I can do” toward “here is something you can see.”

If you would like updates without chasing feeds, RSS is here. If you are hiring or exploring a collaboration and any of this resonates, I would love to hear what you are building—everything worth pointing at is linked from this site.