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. 3 min

    Flower Engineering · Part 3

    Euroia, an Agent for Good Flow 🌻

    Meet Euroia, the AI agent that practises Flower Engineering with me.

    #flower-engineering#euroia#agents

  2. 4 min

    Flower Engineering · Part 2

    How the Work Moves in Flow 🌻

    How Flower Engineering organises the work in three disciplines that never stop, patterns that describe them, and workflows and habits that carry them into practice.

    #flower-engineering#disciplines#patterns#workflows

  3. 4 min

    Flower Engineering · Part 1

    An Introduction to My Personal Methodology 🌻

    Why I built my own methodology to clear turbulence and return to flow, and the nine principles that guide my decisions.

    #flower-engineering#principles#flow

  4. 5 min

    A Garden Full of Beautiful Thoughts 🌸

    The Greek and Zen philosophy behind my AI-powered brain extension, 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 back the flow. Three disciplines shape the work, Strategy, Build, and Care, running side by side rather than as phases. Patterns describe each discipline at its best, workflows carry them into practice, and principles and habits feed the soil beneath it all.

Discipline
A current of work that never really stops. Only its intensity shifts over the life of a project.
Pattern
A modular guideline that channels the current from intention through action to steady state.
Workflow
A sequence of practical steps, built from patterns, that helps humans and agents stay in flow.

  1. Discipline 01 · The slow part

    Strategy

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

    Patterns · 3

    • Strategy Inception

      Once per project

      Turns a raw intention into a README through questions, then shapes the first ideas until the next step is ready to pull.

      Produces · README and first idea

    • Strategy Capture

      Anytime

      Capture anything, anytime, fast. Gives any thought a quick home, from a conversation or the dump, as an idea or issue document.

      Produces · Idea and issue documents

    • Strategy Steering

      As needed

      Orders ideas and issues into milestones, maps dependencies and constraints, and breaks complex work into small steps.

      Produces · Roadmap

  2. Discipline 02 · The finite part

    Build

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

    Patterns · 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.

    Patterns · 1

    • Care Monitoring

      Planned

      Measures the running system against its SLOs: availability, latency and errors. When the error budget runs low, fixing comes before new features.

      Produces · SLOs, dashboards, alerts

Patterns in practice

Workflows

Navigating the currents with selected tools and a defined set of commands.

Workflows · 1

  • Development Workflow

    Per idea

    The everyday path of one idea, from idea document to merged milestone: git branching, OpenSpec commands, and the small fixes that make the patterns hold in practice.

    Applies · Strategy Capture, Build Planning, Build Implementation, Build Documentation

The baseline

Fundamentals

The soil the three disciplines grow from. Principles and habits are its nutrients: what I believe about good work, and what I practice every day. Every discipline draws on them in its own way.

Principles

Lasting beliefs that guide all disciplines.

Collections · 2

  • DevOps Three Ways

    Flow, Feedback and Learning: work moves without piling up, I know early whether it works, and every surprise makes the system better.

  • Flower Flavors

    What Flower adds on top: stupid-simple over clever, self-healing over hand-held, security first.

Habits

Ongoing effort that runs beneath all disciplines.

Habits · 3

  • 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.

  • Seek Feedback

    Treat constructive feedback as precious. Feedback is there to grow from. Ask for it early and often.

  • Measure Flow

    Planned

    Make the flow of work visible: how long an idea takes to ship, how much is in progress at once, and how often work needs redoing.