@fnl
About
Software Architect & Principal Developer | Open Source Leader | Plain Text as Code
With roots in programming since 1984 and a full-time career since 2001, I design and build scalable backend systems running in the Cloud with Kubernetes. I bring many years of experience with Java and Kotlin, and my focus today is on architecture, design, and agentic AI — not just to accelerate delivery, but to fundamentally rethink how software is built.
X as Code — My Manifesto
I believe that anything worth knowing about a system should live as plain text in version control. Infrastructure as Code proved it. Architecture as Code extends it. Plain Text as Code takes it all the way.
If it's not in the repo, it doesn't exist. If it can't be versioned and read by an AI agent, it will rot.
This is the core of my Plain Text as Code manifesto (https://github.com/Plain-Text-as-Code) — a philosophy for structuring software knowledge in an agentic AI age: plain text over proprietary tools, file structure over navigation systems, generated output over stored binaries.
Architecture as Code with AI
I practice and advocate for spec-driven development — keeping architecture and code in sync through ADRs, C4 diagrams, domain models, and OpenSpec, all as plain text. My Architecture as Code example repository (https://github.com/flemming-n-larsen/architecture-as-code-example) is a living reference for this approach.
AI doesn't replace the architect. It amplifies one — if the repo is structured for it. Follow my thinking on this in my blog: Architecture as Code (https://architecture-as-code.hashnode.dev/)
Open Source
Since 2005, I've been the lead maintainer of Robocode, the programming game that has taught generations of developers AI, strategy, and competitive coding. Currently evolving it with Robocode Tank Royale (https://github.com/robocode-dev/tank-royale), and the Book of Robocode is now available at https://book.robocode.dev/
Philosophy
AI and automation should handle the trivial so we can focus on the structural and creative. I prefer clarity over dogma, plain text over dashboards, and questions that matter over answers that are merely convenient.
With roots in programming since 1984 and a full-time career since 2001, I design and build scalable backend systems running in the Cloud with Kubernetes. I bring many years of experience with Java and Kotlin, and my focus today is on architecture, design, and agentic AI — not just to accelerate delivery, but to fundamentally rethink how software is built.
X as Code — My Manifesto
I believe that anything worth knowing about a system should live as plain text in version control. Infrastructure as Code proved it. Architecture as Code extends it. Plain Text as Code takes it all the way.
If it's not in the repo, it doesn't exist. If it can't be versioned and read by an AI agent, it will rot.
This is the core of my Plain Text as Code manifesto (https://github.com/Plain-Text-as-Code) — a philosophy for structuring software knowledge in an agentic AI age: plain text over proprietary tools, file structure over navigation systems, generated output over stored binaries.
Architecture as Code with AI
I practice and advocate for spec-driven development — keeping architecture and code in sync through ADRs, C4 diagrams, domain models, and OpenSpec, all as plain text. My Architecture as Code example repository (https://github.com/flemming-n-larsen/architecture-as-code-example) is a living reference for this approach.
AI doesn't replace the architect. It amplifies one — if the repo is structured for it. Follow my thinking on this in my blog: Architecture as Code (https://architecture-as-code.hashnode.dev/)
Open Source
Since 2005, I've been the lead maintainer of Robocode, the programming game that has taught generations of developers AI, strategy, and competitive coding. Currently evolving it with Robocode Tank Royale (https://github.com/robocode-dev/tank-royale), and the Book of Robocode is now available at https://book.robocode.dev/
Philosophy
AI and automation should handle the trivial so we can focus on the structural and creative. I prefer clarity over dogma, plain text over dashboards, and questions that matter over answers that are merely convenient.
Available for
Nothing here yet.
