Practitioner vs. pundit

There's a version of my career where I only speak and consult. Keynotes, frameworks, advisory retainers. No codebase. No operational responsibility. Clean hands.

That version would probably make more money with less stress. I didn't choose it. Not because I'm virtuous. Because I don't trust advice I haven't tested.

The pundit trap

Pundits optimize for clarity. Practitioners optimize for truth. Those overlap sometimes. Often they don't.

A pundit can say "simplicity creates trust" on stage and collect applause. A practitioner has to make that true in a funeral home website at 11 PM when a family can't find the obituary page, and live with the consequences if it isn't.

The distance between the stage and the codebase is where credibility goes to die. I've watched consultants deliver beautiful strategy decks that nobody could implement. I've watched engineers build flawless products nobody wanted. Both groups were confident. Both were wrong in different directions.

Why I stay in the field

I operate technology in a second-generation family funeral home. I've been in that industry longer than I've been coding. When I recommend a digital approach to a funeral conference audience, it's not theory. It's what I did last month, including the parts that didn't work.

I write Swift and Kotlin. I've cleared App Store rejections for state lottery teams. I've mentored founders from idea to App Store ranking. I founded Lissiland to do this work at scale.

None of that makes me better than people who choose a different path. It makes my writing and speaking harder to fake. When I say a product decision matters, it's because I've felt the cost of ignoring it.

Speaking without pretending

I speak at conferences: NFDA, ICCFA, OGR, and others. I enjoy it. But I refuse to be the person who flies in, delivers inspiration, and leaves before the hard questions start.

My talks are tailored to the room. They include real examples, including failures. I give organizers my slides to keep and modify. I answer emails afterward. Because the talk isn't the product: the behavior change afterward is.

The cost of practicing

Being a practitioner is slower. You can't opine about ten industries. You can't publish weekly hot takes. You say no to things that would dilute your focus.

I'm okay with that trade. This site is my digital garden: ideas that mature over time, tested against real work. Some essays will age badly. I'll revise or replace them. That's the point of a garden, not a billboard.

What I'm not

I'm not a motivational speaker. I'm not an AI influencer. I'm not a generic software engineer listing skills on a resume.

I'm a builder who thinks out loud. The building keeps the thinking honest.