field notes / project lab

Part 4 — Building the machine that explains the builder

The project began as a relatively conventional portfolio rebuild.
At first, the goal was straightforward: create a new home for my work and a more coherent way to present the projects, campaigns and ideas I have developed over the years. That body of work already exists in mikaelbertus.com , where selected projects range from brand campaigns and documentaries to SEO-driven content platforms and large-scale strategic concepts. The site presents the visible output of a career spent working at the intersection of strategy, writing, design and creative direction. But as I began rebuilding the portfolio, it became increasingly obvious that a conventional showcase would not capture the most interesting part of the story. The finished work matters, of course. Yet what has always interested me most are the systems, structures and chains of reasoning that make the work possible in the first place. A campaign is interesting because of the strategic architecture that produced it. A brand platform is interesting because of the insights and conceptual models that gave it shape. A software project is interesting because of the design decisions, technical experiments and developer journal entries that document its evolution. This realization changed the direction of the project. The original plan was to migrate and gradually expand my existing creative and advertising portfolio. That work will be added over time, and it remains an important part of the larger picture. But for the moment, the focus has shifted toward more technical full-stack projects and the systems that support them. This is partly pragmatic. Technical projects are the newest and fastest-growing dimension of my professional development. They also provide a particularly concrete way to demonstrate how strategy, engineering, infrastructure and editorial thinking can be combined into working products. And they are inherently autobiographical. A project such as Mökkisää is not merely an application. It is a record of learning Linux, Docker, deployment, data modelling, probability and interface design in parallel. MikaelOS therefore began to evolve into something more ambitious. First into a technical field notebook. Then into a developer journal. Then into an editorial CMS. Then into a shared publishing engine built on Django, Python and Linux. Projects and essays began to use the same ContentBlock architecture. Creative case studies, strategic essays, technical notes, developer logs and software experiments could all be rendered through a common system. This was not merely an engineering decision. It was autobiographical. The architecture mirrors the professional identity it documents. Different content types. Shared underlying structure. Different disciplines. Common operating principles. The more MikaelOS developed, the clearer it became that the project was simultaneously a portfolio, a laboratory notebook, a developer journal and a theory of work. It is a machine for explaining the builder who built it.

Series

Building MikaelOS

  1. Part 1 — The problem with being difficult to categorize
  2. Part 2 — The polyglot, the generalist and the mad scientist
  3. Part 3 — Personal branding as systems design
  4. Part 4 — Building the machine that explains the builder
  5. Part 5 — The brand going forward