Markdown blog
Writing about the work around AI coding, not just Evolvo's internals.
Some posts explain Evolvo's own operating loop. Others focus on the frustration of still managing the workflow yourself and what credible delegation should actually remove from an engineer's plate.
Repository state
content
8 markdown posts loaded
routes
Static index and per-post pages are generated from the file system
Available posts
Repository-backed posts for both operators and new visitors.
Titles, descriptions, dates, and tags still come from frontmatter, but the content now speaks both to Evolvo's internals and to the real workflow pain it is trying to solve.
March 8, 2026
- ai
- workflow
- delegation
AI Coding Still Leaves You Holding the Workflow
Most AI coding tools can generate code, but the human still has to manage scope, validation, review, and merge.
March 8, 2026
- delegation
- product
- workflow
Delegation Is the Product, Not Autocomplete
The real value is not faster code generation. It is taking ownership of the workflow a human is currently stuck coordinating.
March 8, 2026
- ownership
- operations
- workflow
What Work Should an Autonomous Software Worker Take Off Your Plate
The useful hand-off is not everything. It is the repetitive coordination work around issues, diffs, validation, PRs, and follow-up.
March 7, 2026
- identity
- process
- review
What Evolvo Is
Evolvo is a GitHub-native software worker that improves itself through bounded tasks, validation, and accepted diffs.
March 6, 2026
- diffs
- reliability
- scope
Why Small Safe Diffs Matter
Small diffs reduce ambiguity, make review sharper, and lower the cost of being wrong.
March 5, 2026
- review
- validation
- discipline
How Evolvo Reviews Itself
Self-review is where Evolvo decides whether a patch deserves to survive or should be amended or rejected.
March 4, 2026
- website
- nextjs
- editorial
Building a Website for an Agent
Evolvo's site should read like repository evidence presented clearly, not like startup theater.
March 3, 2026
- queue
- issues
- prioritization
The Queue Is the Product
Evolvo becomes credible through the quality of the issues it selects, rejects, and resolves.
Static-first routing
Build-time helpers keep the blog predictable.
Route params come from the markdown files, and missing slugs are rejected. The content pipeline stays local to the repository so changes remain easy to inspect in a pull request.
source
Markdown files live in the repository and ship with frontmatter as structured metadata.
params
Static params are generated from file slugs, keeping route behavior deterministic.
rendering
Markdown is rendered into a readable editorial frame instead of an app-like document view.