About maintainable.software
maintainable.software is a publication about agentic engineering, software architecture, docs-first product development, and maintainable software delivery. The focus is not AI as a magic code generator, but AI as leverage for serious engineering work: structuring codebases, improving feedback loops, making better technical decisions, and shipping software that stays understandable over time.
What is maintainable.software about?
Agentic engineering is moving quickly, but a lot of the available advice is either shallow, overly tool-driven, or disconnected from what makes software maintainable in the first place. This blog exists to close that gap. It covers how to use coding agents and AI-assisted workflows without giving up clarity, ownership, architecture, or product quality.
The goal is to publish writing that helps readers think better about the work itself, not just copy tactics. That includes durable principles, practical heuristics, and concrete examples that can be applied across different codebases and teams.
Who is this blog for?
It is written for software engineers, technical leads, architects, and independent builders who want to use AI seriously rather than casually. If you care about long-term code quality, system design, responsibility boundaries, documentation, and feedback loops, this is the intended audience.
What kind of topics does it cover?
The blog focuses on questions such as:
- How to design codebases that are easier for coding agents to navigate safely
- How documentation, guardrails, and tests change AI-assisted delivery
- How to think about software architecture in an agentic workflow
- How docs-first product development improves implementation quality
- How to keep AI-assisted work maintainable instead of merely fast
What perspective does the publication take?
The perspective is opinionated, practical, and grounded in software engineering experience. The writing is less interested in hype, prompt theater, and one-off hacks, and more interested in how AI can support real product and systems work. That means maintainability, resilience, verification, and architectural judgment matter at least as much here as raw output speed.
Publication and author
maintainable.software is the publication. It is written by Jan-Gerke Salomon, an independent software engineer with a strong frontend foundation, full-stack delivery experience, and a current focus on agentic engineering and software architecture.
The canonical author page lives at /me/, where Jan-Gerke Salomon's background, experience, and external profiles are collected in one place.
Where should you start?
Browse the homepage for the essays themselves or visit /me/ if you want the author context behind the publication.