Grow log · the page you are reading
this talk
Five days, from "which angle should I take?" to this site, its 45 films and these grow logs. The talk was grown the same way as everything in it.
- requests typed
- 39
- commits
- 18
- days with work
- 5
- first to last prompt
- 11 Nov – 15 Nov
11 Nov13 Nov15 Nov
13 a day at most
The seed
11 November 2026, the first prompt
I need to give a talk to teachers ICT (HBO level, the Netherlands) and I want to show off my work on projects with claude code. I have a couple of angles I can take but I can't choose: […]
Can you give me some advice on what angle to choose, what projects I can show to make some of my points and what structure the talk should have. I have 60 minutes. […]
I want to show this to make the parallel with growing vs building: can a farmer be proud of their crop? They didn';t build it themselves? But they tok the initiative to plant the seed, care for the crop and decide when to harvest. Not caring for a crop rarely gives a good result. You need to put in the time. Software development is starting to look a lot more like farming and less like building.
A pasted list of possible angles, and one idea I could not let go of.
How it grew
-
11 November
Choosing an angle
Claude read my conversations and projects, and wrote an outline and a page of statistics.
look at conversations on this machine and the projects that I have built. I want to show off as much projects I can, especially the ones that are interesting for education.
-
11–12 November
First, tend the seed
knowledge-farm, the word-association tree that grows a report, got images from vonk, report styles, Dutch or English, and a login before it went on stage.
Add a style selector for the reports to the knowledgefarm. For each style there's a prompt: business report, prose, poetic, commercial flyer.
-
12 November
A website, not a PowerPoint
A seed catalogue to present from, starting with the Fab Academy work of 2022: built by hand, right before AI.
I want to turn this into a website rather than a powerpoint.
Use the front-end design skill to make it less AI looking.
-
12–14 November
A film for every packet
Hero shots and a brag film for every project. All 45 films were made three times, the last time without music and from scratch.
redo all the brag videos without music. I deleted the brag-output folder so you wouldn;t be tempted to recycle the old scripts.
-
13 November
The story finds its shape
The quiet years after the Fab Academy, the AI slowly taking over my loop, and a background that starts as bricks and turns to soil at Game Babies.
dont mention farming at the start. start the backgroundvwith bricks and transition a farming theme to around gamebabies and knowledge farm.
Everytime I clicked on "accept all changes" without looking too much at the code I felt a little ashamed.
-
15 November
Show the farm, keep the gate shut
A map of my setup that names roles, not addresses. The machines that made playing free. Text I can edit on the page itself. And these grow logs.
Decide wether some information can be a security hazard of too many poeple would know.
Allow me to edit all of the text on the site "in place", store it as a template and re-bake the changes into the site.
Tending for quality
A plan, then the work
Plan mode for each big change; the speaker notes in outline.md kept in step with the site.
Checked like a visitor
After every change, screenshots at projector size and at phone width, and a check for sideways scrolling.
Nothing on screen that shouldn't be
No keys, no internal addresses, no student or colleague names. Personal apps without their address; the setup as roles.
Films checked frame by frame
Every film passes a layout and contrast check and a look at stills before it is rendered.
Words stay editable
Press e: the text is edited in place, cleaned, baked into the page, with tests for the editor.
Small commits, no surprises
One commit per change, and nothing pushed or deployed without asking.






