Lars Barkman
writings/work/resume/

Independent consultant · Solopreneur

Hi, I'm Lars Barkman.

I help enterprises design, develop, and operate digital solutions they can rely on — and I build the models and tooling behind it, for them and for markets I’m part of myself.

The writings are where I think in the open — catching myself in the act of thinking, testing a position, or arriving at an understanding I only thought I had.

The work spans three areas, each approached as knowledge, tooling, and services — consulting the most direct of them, and the rest where I stop describing problems and start building.

The resume is the 20+ years that led here — the same instinct running through all of it: to understand how things really work, and to make them work better.

Get in touch

Writings

See all writings

Notes on organizations, technology, and the full lifecycle of digital solutions — from tactical detail to strategic perspective.

  • Aug 5, 2026solopreneurship
    Self-Hosting My Repositories and Sites
    The follow-up to choosing a host: what it actually takes to run Forgejo per area, wire it to Cloudflare through Wrangler, and serve self-hosted sites behind a CDN using the RAD Stack's ingress layer.
  • Aug 5, 2026solopreneurship
    Choosing a Host for My Open Repositories
    Where should the public parts of my work live — on Codeberg, on GitHub, or on my own infrastructure? Codeberg's new terms exclude projects built with heavy LLM use, which is the honest description of how I work. Taking that objection seriously points at self-hosted Forgejo, and at paying for the load I generate.
  • Jul 28, 2026solution-design
    Choosing a Versioning Scheme
    A structured look at how releases get numbered — SemVer, CalVer, ZeroVer, rolling integers, marketing names, and commit hashes — what each one actually promises its reader, and why my pre-1.0 ventures are moving to date-based releases with SemVer held back for 1.0.

Work

See all work

Everything I am involved in, in one view — three areas spanning retail systematic trading, the digital solution life cycle, and enterprise operating, each worked as knowledge, tooling, and services.

  • Digital Solution Life Cycle Model — Team Enablement
    Teaching a delivery team the DSLC Model and getting them running it on their own portfolio — classification, ownership, and process applied to real work, not generic capability building.
  • Enterprise Operating Model — Team Enablement
    Teaching a management team the EO Model and getting them exercising it on real decisions — ownership and decision rights applied to your actual organization, not generic leadership development.
  • Solution Architect (Interim)
    Stepping in as solution architect — designing the architecture, leading the technical decisions, and staying hands-on through delivery.
  • Enterprise Architect (Interim)
    Stepping in as enterprise architect — clarifying ownership, shaping the operating model, and making the structural decisions that unblock delivery.
© 2026 • Lars Barkman