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
40 lines
1.8 KiB
Markdown
40 lines
1.8 KiB
Markdown
---
|
|
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.
|