sjat/MakerFLOSS
1
1
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

slides(tappaas): the predecessor ran five years; 2-3 artefacts before coding
All checks were successful
Build docs site / build (push) Successful in 43s
Details
Build slides / build (push) Successful in 1m5s
Details

Browse source 
Last TODO closed: the pre-TAPPaaS setup ran five years uninterrupted and never
had a name.

Guardrail 1 now says 2-3 artefacts rather than three — the Issue is always
there, the ADR and the plan only when the change warrants them.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Lars Rossen 2026-08-25 18:19:58 +02:00
parent 2e16c4a16b
commit 66b20ffc06
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
slides/tappaas/one-year-in/index.md
View file

@ -467,8 +467,9 @@ TODO: your own hours-per-week number makes the concession land harder.
**No. There have been at least two large rewrites — and a whole system before this one.** **No. There have been at least two large rewrites — and a whole system before this one.**
- **The predecessor.** I ran a hand-built setup for a few years before TAPPaaS - **The predecessor.** Before TAPPaaS existed I ran a hand-built setup for
existed. Every design decision here is an argument I already lost once, at home. **five years, uninterrupted**. It never had a name. Every design decision
here is an argument I already lost once, at home.
- **Rewrite 1 — ADR-003.** Every module was a plain `install.sh` you ran in the - **Rewrite 1 — ADR-003.** Every module was a plain `install.sh` you ran in the
right order, by hand. Replaced by `dependsOn` / `provides` contracts, resolved right order, by hand. Replaced by `dependsOn` / `provides` contracts, resolved
into an install order by the platform. into an install order by the platform.
@ -479,8 +480,6 @@ TODO: your own hours-per-week number makes the concession land harder.
Both times the same mistake: I had written as a **sequence of steps** Both times the same mistake: I had written as a **sequence of steps**
what needed to be a **structure** — dependencies the first time, roles the second. what needed to be a **structure** — dependencies the first time, roles the second.
`TODO: name the predecessor, and say how long you ran it`
<!-- <!--
This is the credibility slide. Do not soften the "No" — an audience that has This is the credibility slide. Do not soften the "No" — an audience that has
just been told you gave an AI root needs to hear that you rebuild things when just been told you gave an AI root needs to hear that you rebuild things when
@ -558,7 +557,8 @@ transferable to anyone in the tent using these tools.
## Guardrail 1 — nothing starts with a prompt ## Guardrail 1 — nothing starts with a prompt
By the time the AI is allowed to type, three humans-only artefacts exist: By the time the AI is allowed to **code**, 2–3 artefacts exist —
carefully crafted and reviewed by humans:
1. **An Issue** — a well-defined problem and a proposed fix. No issue, no change. 1. **An Issue** — a well-defined problem and a proposed fix. No issue, no change.
2. **An ADR**, for anything non-obvious — reviewed by **at least two people**. 2. **An ADR**, for anything non-obvious — reviewed by **at least two people**.