Flowers of Eunoia

Flow Oriented · Privacy Focused · Human Centered

A Value Stream of Quiet Thoughts Sourced from Eunoia

Welcome to the public window into my personal vault. Here, I share my philosophy from flow to flower, my approach to digital smallholding with a K3s cluster, and my reflections on personal privacy and sovereignty.

Read my Writing

Latest

Recent Writing

All writing

  1. 2 min

    A Garden Full of Beautiful Thoughts 🌸

    The Greek and Zen philosophy behind my AI-powered brain extention, and why its AI gardener keeps order but never leads.

    #eunoia#mushin#knowledge-management

Methodology

Flower Engineering

Flower Engineering is how I approach technical challenges in IT. I work to calm the turbulence in technology value streams and strive for laminar flow: work that moves smoothly from intention to steady state. But no flow stays laminar forever. Turbulence always returns, and that is where Flower begins. Flower is flow, made flow-er, and the beauty of a real flower: someone has to plant it and grow it, and it stays beautiful only while they keep tending it. Flower is all of that: building boringly simple systems, and making small, continuous improvements that bring the flow back. Three disciplines carry the practice, Strategy, Build, and Care, running side by side rather than as phases, with habits beneath all three.

Discipline
A kind of work that never stops. Only its weight shifts over the life of a project.
Workflow
A guide with steps, an entry and an exit. Each belongs to exactly one discipline.
Habit
Work with no wave of its own: it runs flat under every discipline, every day, and each discipline carries it out in its own way.

  1. Discipline 01 · The slow part

    Strategy

    Exploring the problem to be solved and deciding on the solution to be built.

    Workflows · 3

    • Strategy Birth Once per project

      Cascades vision, principles and concept, each phrased by me and refined with an AI agent, and seeds the first roadmap.

      Produces · Vision, concept, roadmap

    • Strategy Capture Anytime

      Captures thoughts fast and raw: a one-liner in the dump, or an idea document when an idea needs room to grow.

      Produces · Dump lines, idea docs

    • Strategy Steering Weekly

      Drains the dump into roadmap entries, decisions or the trash, and puts the roadmap back in order.

      Produces · Roadmap

  2. Discipline 02 · The finite part

    Build

    Pipelines, infrastructure as code and automation, until deployment and provisioning get boring.

    Workflows · 3

    • Build Planning At the pull

      Sets the appetite and acceptance check, records one-way decisions as ADRs, and shapes the tasks in an OpenSpec proposal.

      Produces · ADRs, OpenSpec proposal

    • Build Implementation Per milestone

      Works through the tasks, sends wrong assumptions back to Strategy, and closes the milestone against its acceptance check.

      Produces · Closed milestone

    • Build Documentation Every build day

      A build log every day, a build report at milestone close, and blog drafts whenever. Structure loosens as the audience widens.

      Produces · Log, report, blog

  3. Discipline 03 · The long part

    Care

    Monitoring, SRE in practice, and the improvement loops that keep a system flowing after everyone has stopped looking at it.

    Workflows · 0

    No workflows yet.

The baseline

Habits

The soil the three waves grow from. Every discipline carries them out in its own way.

Habits · 2

  • Document progress

    Write it down while it's warm, in the shape its reader needs. A decision that was never written down gets made twice.

  • Grow through feedback

    Noticing obliges acting. When later work proves earlier work wrong, go back and amend it; don't patch around it.