docs(okf): record learning contract and boss-facing German plan
learning contract: 2 h company time per week plus evenings, 6-month learning phase, German one-pager per module, repo goes public; add lern-und-entwicklungsplan.md and modul-zusammenfassung.md template; language model fixed browser-only; resolve open questions
This commit is contained in:
1 parent
f0a9d58cff
commit
6ab76c2a36
6 files changed
+197
-3
No files matched your search
@@ -0,0 +1,39 @@
|
|||||||
|
---
|
||||||
|
type: Decision
|
||||||
|
title: Learning contract with PreZero
|
||||||
|
description: 2 hours of company time per week plus evenings on this project during a 6-month learning phase; a German one-pager per finished module; the repo goes public so the boss can follow by link.
|
||||||
|
tags: [decision, learning, prezero]
|
||||||
|
status: stable
|
||||||
|
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-15T00:00:00Z }
|
||||||
|
verified: { by: human:noel, at: 2026-10-15T00:00:00Z }
|
||||||
|
---
|
||||||
|
|
||||||
|
# Decision
|
||||||
|
|
||||||
|
Noel, developer in the AI & Digitalization department, runs this project as a
|
||||||
|
personal learning project within an agreed **6-month learning phase**:
|
||||||
|
|
||||||
|
- **2 hours of company time per week**, the rest in the evenings, on Noel's
|
||||||
|
own server. No company data, no company secrets, no company cost.
|
||||||
|
- **No hard delivery promise.** After 6 months both sides review how far the
|
||||||
|
work has come; the follow-up phase is decided then.
|
||||||
|
- **One German one-pager per finished module** (template:
|
||||||
|
[`modul-zusammenfassung.md`](/modul-zusammenfassung.md)): what was built,
|
||||||
|
what was learned, relevance for the team, and proof.
|
||||||
|
- **The Gitea repository becomes public**, so the boss can follow progress by
|
||||||
|
link. The [Lern- und Entwicklungsplan](/lern-und-entwicklungsplan.md) in
|
||||||
|
this bundle is the document he reads.
|
||||||
|
|
||||||
|
# Why
|
||||||
|
|
||||||
|
- The AI & Digitalization department builds webapps and missing tooling.
|
||||||
|
This project exercises exactly that delivery path: containers, orchestration,
|
||||||
|
infrastructure as code, CI/CD and observability — on a day job's real stack.
|
||||||
|
- The boss explicitly wants the team to get better; this makes the learning
|
||||||
|
visible and reviewable instead of invisible.
|
||||||
|
- Direction to senior developer: demonstrating ownership across the full
|
||||||
|
delivery chain, not only writing features.
|
||||||
|
|
||||||
|
# Revisit when
|
||||||
|
|
||||||
|
The 6-month review happens, or company time availability changes.
|
||||||
@@ -4,7 +4,7 @@ title: Open questions
|
|||||||
description: Decisions still to make, with the release that needs each answer.
|
description: Decisions still to make, with the release that needs each answer.
|
||||||
tags: [decision, open]
|
tags: [decision, open]
|
||||||
status: draft
|
status: draft
|
||||||
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-11T12:15:30Z }
|
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-15T00:00:00Z }
|
||||||
---
|
---
|
||||||
|
|
||||||
| Question | Needed by | Default if nobody decides |
|
| Question | Needed by | Default if nobody decides |
|
||||||
@@ -12,10 +12,13 @@ generated: { by: claude-code/claude-opus-5-5, at: 2026-10-11T12:15:30Z }
|
|||||||
| Final chapter list and the state of each chapter | 0.3.0 (placeholders), 1.0.0 (final) | Four placeholder chapters: one completed, one active, one unfinished, one failed |
|
| Final chapter list and the state of each chapter | 0.3.0 (placeholders), 1.0.0 (final) | Four placeholder chapters: one completed, one active, one unfinished, one failed |
|
||||||
| Story card text per chapter | 0.9.0 | None, Noel writes it |
|
| Story card text per chapter | 0.9.0 | None, Noel writes it |
|
||||||
| Life map visual form: timeline, graph or map | 0.9.0 | Vertical timeline |
|
| Life map visual form: timeline, graph or map | 0.9.0 | Vertical timeline |
|
||||||
| Approve Terraform for server provisioning | 0.2.0 | Do it, infra as code is the point |
|
|
||||||
| Which Gitea release-please action, exact name | 0.1.0 | None, Noel names it |
|
| Which Gitea release-please action, exact name | 0.1.0 | None, Noel names it |
|
||||||
| How the server is reachable: router port-forward, static IP or DDNS | 0.4.0 | DDNS + port-forward 80/443 |
|
| How the server is reachable: router port-forward, static IP or DDNS | 0.4.0 | DDNS + port-forward 80/443 |
|
||||||
| k6 staging target: namespace or separate cluster | 1.2.0 | Namespace `cv-staging` on the same cluster |
|
| k6 staging target: namespace or separate cluster | 1.2.0 | Namespace `cv-staging` on the same cluster |
|
||||||
| WebMCP scope: state read-only, or state plus push | 1.1.0 | State plus push, same limits as visitors |
|
|
||||||
| Approve PyTorch for the language model | 1.5.0 | None, needs Noel |
|
| Approve PyTorch for the language model | 1.5.0 | None, needs Noel |
|
||||||
| Approve NumPy (or similar) for the own autograd engine | 1.13.0 | None, needs Noel |
|
| Approve NumPy (or similar) for the own autograd engine | 1.13.0 | None, needs Noel |
|
||||||
|
|
||||||
|
Resolved since the last review: Terraform approved (0.2.0), WebMCP scope
|
||||||
|
decided — state plus push, exposed from the Nuxt page, same limits as
|
||||||
|
visitors (1.1.0), Caddy instead of nginx (0.4.0), browser-only language
|
||||||
|
model (after 1.7.0), and the [learning contract](/decisions/learning-contract.md).
|
||||||
@@ -8,6 +8,10 @@ okf_version: "0.2"
|
|||||||
* [Roadmap](roadmap.md) - Small releases in three phases, each a few days of work at most, each ending in something that runs.
|
* [Roadmap](roadmap.md) - Small releases in three phases, each a few days of work at most, each ending in something that runs.
|
||||||
* [Update log](log.md) - History of changes to this bundle.
|
* [Update log](log.md) - History of changes to this bundle.
|
||||||
|
|
||||||
|
# Für den Vorgesetzten
|
||||||
|
|
||||||
|
* [Lern- und Entwicklungsplan](lern-und-entwicklungsplan.md) - Der deutsche Plan: was ich baue, was ich lerne, wie Fortschritt messbar wird.
|
||||||
|
|
||||||
# Drill down
|
# Drill down
|
||||||
|
|
||||||
* [Architecture](architecture/) - Components, services, frontend, delivery, and the in-browser language model.
|
* [Architecture](architecture/) - Components, services, frontend, delivery, and the in-browser language model.
|
||||||
|
|||||||
@@ -0,0 +1,111 @@
|
|||||||
|
---
|
||||||
|
type: Lernplan
|
||||||
|
title: Lern- und Entwicklungsplan
|
||||||
|
description: Deutschsprachiger Plan für meinen Vorgesetzten — was ich baue, was ich lerne, wie Fortschritt messbar wird.
|
||||||
|
tags: [lernplan, prezero, deutsch]
|
||||||
|
status: stable
|
||||||
|
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-15T00:00:00Z }
|
||||||
|
---
|
||||||
|
|
||||||
|
# Zusammenfassung
|
||||||
|
|
||||||
|
> **TL;DR: In einer 6-monatigen Lernphase baue ich auf meinem eigenen Server
|
||||||
|
> eine interaktive CV-Website, auf der jedes Lebenskapitel als echtes System
|
||||||
|
> läuft, das man umwerfen und sich wieder aufrichten sehen kann. Dafür lerne
|
||||||
|
> ich die komplette moderne Lieferkette — Infrastruktur als Code, Container,
|
||||||
|
> Kubernetes, automatisierte Pipelines und load testing — genau die
|
||||||
|
> Werkzeuge, die unser Team (AI & Digitalization) beim Bauen von Webapps und
|
||||||
|
> Werkzeugen täglich braucht. 2 Stunden Firmenzeit pro Woche plus Abende,
|
||||||
|
> alles auf eigener Infrastruktur, keine Kosten für PreZero. Nach jedem
|
||||||
|
> fertigen Modul schreibe ich einen One-Pager (Was gebaut / Was gelernt /
|
||||||
|
> Relevanz fürs Team / Beweis). Fortschritt ist jederzeit sichtbar im
|
||||||
|
> Repo.**
|
||||||
|
|
||||||
|
# Ausgangslage
|
||||||
|
|
||||||
|
Ich bin Developer in der Abteilung AI & Digitalization — wir bauen fehlende
|
||||||
|
Tools, Webapps und helfen strategisch bei der Digitalisierung. Mein Ziel ist
|
||||||
|
es, über Skill und Kenntnis in Richtung Senior-Developer zu wachsen. Der
|
||||||
|
direkteste Weg dafür: ein echtes Produkt bauen, betreiben und nachweisbar
|
||||||
|
verbessern — nicht in einer Sandkastenumgebung, sondern im echten Betrieb.
|
||||||
|
|
||||||
|
# Das Projekt in vier Sätzen
|
||||||
|
|
||||||
|
Meine CV-Website serviert zunächst den professionellen Regelbetrieb — Name,
|
||||||
|
Kontakt, PDF, in 10 Sekunden verstanden. Darunter läuft jedes Lebenskapitel
|
||||||
|
als echter Service auf meinem k3s-Cluster ("schlankes Kubernetes"): Besucher
|
||||||
|
können ein Kapitel umwerfen und zusehen, wie es in gemessenen Sekunden
|
||||||
|
wieder hochkommt. Failures sind bewusste Inhalte ("Lektion gelernt"), kein
|
||||||
|
Bug. Das Projekt zeigt damit exakt, was im Job zählt: Systeme bauen,
|
||||||
|
die ausfallen und wieder aufstehen.
|
||||||
|
|
||||||
|
# Warum das für unser Team relevant ist
|
||||||
|
|
||||||
|
Unser Team baut Webapps und Tooling. Dieses Projekt durchläuft genau die
|
||||||
|
Lieferschritte, die wir dafür täglich brauchen:
|
||||||
|
|
||||||
|
| Fähigkeit | Direkte Anwendung im Team |
|
||||||
|
|---|---|
|
||||||
|
| Infrastruktur als Code (Terraform) | Server-Umgebungen reproduzierbar und versionierbar aufbauen |
|
||||||
|
| Container & Kubernetes (Docker, k3s) | Webapps portabel, skaliert und mit Limits betreiben |
|
||||||
|
| Automatisierte Pipelines (CI/CD, Snyk) | Testen, scannen und ausliefern ohne manuelle Schritte |
|
||||||
|
| Eigener Reverse-Proxy (Caddy) | Verstehen, was zwischen Browser und Container passiert |
|
||||||
|
| Beobachterbarkeit (SSE, Logs) | Live-Systeme sichtbar machen, Probleme früh erkennen |
|
||||||
|
| Kontrolliertes Load-Testing (k6) | Wissen, wie viel Last ein Service trägt — ohne Schätzung. |
|
||||||
|
|
||||||
|
Jedes Modul endet mit einem One-Pager: kurz, auf Deutsch, mit Beweis. So
|
||||||
|
wird Lernen messbar statt gefühlt.
|
||||||
|
|
||||||
|
# Der Lernplan
|
||||||
|
|
||||||
|
Die Module bauen aufeinander auf (Reihenfolge = Abhängigkeiten). Zeitwerte
|
||||||
|
sind Fokustag-Estimates, keine Deadlines; insgesamt rund 20–25 Fokustage.
|
||||||
|
|
||||||
|
| # | Modul | Was ich lerne |
|
||||||
|
|---|---|---|
|
||||||
|
| 1 | Restartbarer Chapter-Service | Software bauen, die den Neustart als Feature nutzt |
|
||||||
|
| 2 | Server als Terraform-Code | Kompletten Server zerstörbar & neu aufbaubar machen |
|
||||||
|
| 3 | Kapitel auf k3s | Workloads mit Limits, Labels und Services betreiben |
|
||||||
|
| 4 | Eigener Caddy-Proxy, DNS, TLS | Den gesamten Request-Pfad selbst besitzen |
|
||||||
|
| 5 | CI/CD-Pipeline | Ein `git push` reicht bis zum laufenden Cluster |
|
||||||
|
| 6 | Live-Status (SSE) | Echte Systemzustände sicher an Besucher streamen |
|
||||||
|
| 7 | Knockdown mit Limits | Öffentliche Endpunkte gegen Missbrauch absichern |
|
||||||
|
| 8 | Professioneller First-Screen | Läuft ohne JavaScript, degradiert sauber |
|
||||||
|
| 9 | Life Map & Story Cards | Systemereignisse für Nicht-Techniker erzählbar machen |
|
||||||
|
| 10 | Eigener Tracker + Launch | Ohne Cookies tracken, Privacy by design, fertigstellen |
|
||||||
|
|
||||||
|
Danach, noch in den 6 Monaten, ambitioniert:
|
||||||
|
|
||||||
|
| # | Modul | Was ich lerne |
|
||||||
|
|---|---|---|
|
||||||
|
| 11 | WebMCP | Die Seite wird über die Browser-Schnittstelle für KI-Agenten bedienbar — ohne neue Server-Berechtigungen |
|
||||||
|
| 12 | k6 als Release-Gate | Performanz wird zum Blocker-Kriterium im Release, öffentlich sichtbar |
|
||||||
|
| 13 | Autoscaling-Demo | Skalierung unter Last live sichtbar machen (mehr Repliken unter Last, weniger danach) |
|
||||||
|
|
||||||
|
Erste Phase nach den 6 Monaten: ein kleines, selbst trainiertes
|
||||||
|
Sprachmodell, das komplett **im Browser** läuft und seine Funktionsweise
|
||||||
|
live zeigt — Chat-Fähigkeit und Training von Grund auf, ohne fremde API.
|
||||||
|
|
||||||
|
# Modalitäten
|
||||||
|
|
||||||
|
- **2 Stunden/Woche auf Firmenzeit**, den Rest in den Abenden; beide Anteile
|
||||||
|
laufen auf meinem eigenen Server.
|
||||||
|
- **Keine Kosten, keine Firmendaten, keine Firmengeheimnisse** im Projekt.
|
||||||
|
- Mein **Gitea-Repo wird öffentlich**: Fortschritt, Releases und die Live-Seite
|
||||||
|
sind per Link sichtbar — Sie können beliebig häufig selbst nachsehen.
|
||||||
|
- **Keine harte Deadline:** Die 6 Monate sind mein Taktstock. Danach
|
||||||
|
gemeinsame Bilanz, wie weit ich gekommen bin und was als Nächstes kommt.
|
||||||
|
|
||||||
|
# Messbarkeit
|
||||||
|
|
||||||
|
1. **One-Pager pro Modul** (Vorlage: `modul-zusammenfassung.md`): Was gebaut,
|
||||||
|
was gelernt, Relevanz fürs Team, Beweis (Link, Screenshot, Log).
|
||||||
|
2. **Sichtbarer Fortschritt im Repo:** Releases, Tests, Pipeline und die
|
||||||
|
Live-Seite selbst sind die Beweise.
|
||||||
|
3. **Halbzeitbilanz** nach ca. 3 Monaten: kurzer Stand, was läuft, was
|
||||||
|
gelernt wurde.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
*Quelle: die Planungsdokumente in diesem Bundle (`OKF_CV_Website/`) —
|
||||||
|
Übersicht, Architecture, Entscheidungen und Roadmap.*
|
||||||
@@ -1,5 +1,12 @@
|
|||||||
# Update Log
|
# Update Log
|
||||||
|
|
||||||
|
## 2026-10-15
|
||||||
|
* **Creation**: Added the [Lern- und Entwicklungsplan](/lern-und-entwicklungsplan.md) (German, for the boss at PreZero) and the [Modul-Zusammenfassung template](/modul-zusammenfassung.md) — one German one-pager per finished module.
|
||||||
|
* **Decision**: Recorded the [learning contract](/decisions/learning-contract.md): 2 h company time per week plus evenings, 6-month learning phase, one-pager per module, Gitea repo goes public.
|
||||||
|
* **Update**: Switched the reverse proxy from nginx to **Caddy** everywhere [own proxy](/decisions/own-proxy.md), [Terraform](/architecture/terraform.md), [system](/architecture/system.md), [gateway](/architecture/gateway.md), [roadmap](/roadmap.md) — automatic HTTPS instead of certbot.
|
||||||
|
* **Update**: Language model fixed as **browser-only**; a server-inference variant is cut. See [language model](/architecture/language-model.md).
|
||||||
|
* **Cleanup**: Resolved open questions: Terraform approved, WebMCP scope (state plus push from the page), Caddy, browser-only model. See [open questions](/decisions/open-questions.md).
|
||||||
|
|
||||||
## 2026-10-14
|
## 2026-10-14
|
||||||
* **Direction change**: No Cloudflare Tunnel. The apex domain points straight at the home server; nginx (installed by Terraform with certbot TLS) is the only public entry. See [own proxy](/decisions/own-proxy.md).
|
* **Direction change**: No Cloudflare Tunnel. The apex domain points straight at the home server; nginx (installed by Terraform with certbot TLS) is the only public entry. See [own proxy](/decisions/own-proxy.md).
|
||||||
* **Decision**: Add [Terraform provisioning](/architecture/terraform.md): packages, swap, k3s, nginx and DNS are code; workloads inside the cluster stay with kustomize. See [decision](/decisions/provision-with-terraform.md).
|
* **Decision**: Add [Terraform provisioning](/architecture/terraform.md): packages, swap, k3s, nginx and DNS are code; workloads inside the cluster stay with kustomize. See [decision](/decisions/provision-with-terraform.md).
|
||||||
|
|||||||
@@ -0,0 +1,30 @@
|
|||||||
|
---
|
||||||
|
type: Template
|
||||||
|
title: Modul-Zusammenfassung (One-Pager)
|
||||||
|
description: Pro fertigem Modul ausfüllen — was gebaut, was gelernt, Relevanz fürs Team, Beweis.
|
||||||
|
tags: [template, learning, deutsch]
|
||||||
|
status: draft
|
||||||
|
generated: { by: claude-code/claude-opus-5-5, at: 2026-10-15T00:00:00Z }
|
||||||
|
---
|
||||||
|
|
||||||
|
# Modul: `<Name>` — `<Datum>`
|
||||||
|
|
||||||
|
**Was habe ich gebaut?**
|
||||||
|
|
||||||
|
<!-- 2–4 Sätze, Ergebnis orientiert. Link zum Artefakt, falls es eins gibt. -->
|
||||||
|
|
||||||
|
**Was habe ich gelernt?**
|
||||||
|
|
||||||
|
<!-- 3–5 konkrete Punkte, jeder mit Bezug zur Praxis. -->
|
||||||
|
|
||||||
|
**Relevanz für AI & Digitalization**
|
||||||
|
|
||||||
|
<!-- Wie hilft das unserem Team: Muster, Werkzeuge, Prozesse, die wiederverwendbar sind. -->
|
||||||
|
|
||||||
|
**Beweis**
|
||||||
|
|
||||||
|
<!-- Link, Screenshot, Ausgabe des Done-Checks, Release-Log. -->
|
||||||
|
|
||||||
|
**Wie ist es gelaufen?**
|
||||||
|
|
||||||
|
<!-- Umfang (Zeit), Blocker, was ich beim nächsten Mal anders mache. -->
|
||||||
Reference in new issue
Block a user