Add permacomputer blog post & update writing style guide

This commit is contained in:
Russell Ballestrini 2025-10-17 08:53:31 -04:00
parent cb146ecd5b
commit 8f78d1b474
2 changed files with 179 additions and 0 deletions

View file

@ -82,3 +82,10 @@ Git operations can be destructive to uncommitted work. Always preserve user's wo
- After using a helper script, delete it from the working directory
- Do not include helper scripts in git commits unless specifically instructed
- Focus commits on actual content changes, not the tools used to make them
## WRITING STYLE
**Use "&" instead of "and" most of the time in posts**
- Prefer concise ampersand (&) for connecting words & phrases
- Example: "disrupt wheels & foster open collaboration" not "disrupt wheels and foster open collaboration"
- This creates a more casual, punchy writing style that matches the brand voice

View file

@ -0,0 +1,172 @@
Growing a 454-page ML reference manual in 5 days: permacomputer harvest
########################################################################
:author: Russell Ballestrini
:slug: growing-a-book-in-5-days-ml-and-devops
:date: 2025-10-16 12:00
:tags: Machine Learning, DevOps, Automation, Python, unturf.
:status: published
We just harvested `uncloseai: Machine Learning Inference Client Reference Manual <https://shop.unturf.com/p/8486f492-a93e-11f0-b477-02dfe05770ee/uncloseai-machine-learning-reference-guide-to-inference-clients>`_. 454 pages. 57 implementations across languages. 5 days from seed to harvest (October 11-16, 2025).
This seems like permacomputer agriculture. We don't write books. We grow them.
the permacomputer
=================
At `unturf. <https://www.unturf.com/>`_ we're building a permacomputer. Not a machine. An ecosystem.
Permaculture grows food by working with nature instead of against it. Plant the right seeds, create the right conditions, let systems self-organize & harvest continuously.
Permacomputer grows software the same way. Plant code templates, create automation pipelines, let ML models generate variations & harvest continuously.
Traditional software development: manual labor, row crops, monoculture.
Permacomputer: polyculture, automation, continuous harvest.
the seed
========
Day 1: plant reference implementations by hand.
Python with requests. Python with httpx. C with libcurl.
These are seed stock. Genetic templates. Everything else grows from these.
Each implementation contains the DNA:
- HTTP client patterns
- Request formatting
- Response parsing
- Error handling
- Streaming support
- Docker containerization
the growth cycle
================
**Days 2-3: propagation**
ML models read the seed implementations. Generate 57 variations across languages.
.. code-block:: python
for lang in languages:
# Feed seed DNA to ML
code = ml_generate(seed_implementations, target_language=lang)
plant(lang, code)
Rust, Zig, Odin, Nim, Crystal, JVM languages, .NET, functional languages, scripting languages. All sprouting from the same genetic base.
**Days 2-4: automated cultivation**
Every implementation goes through the cultivation pipeline:
.. code-block:: bash
for impl in implementations/*; do
docker build -t test-$impl $impl
docker run -d -p 8080:8080 test-$impl
curl http://localhost:8080/v1/chat/completions -d '{...}'
python test_streaming.py
docker stop $(docker ps -q)
done
Failed builds get flagged. Regenerate. Test again. The pipeline runs 24/7.
Wake up to 10-15 new implementations tested and validated.
**Days 4-5: harvest**
ML generates documentation from working code. We review, edit, format & assemble the book.
Template → generation → validation → harvest.
the permacomputer mindset
=========================
**1. ML as mycelium**
Mycelium breaks down organic matter & distributes nutrients. ML breaks down reference code & distributes patterns across languages.
Not replacement. Decomposition and propagation.
**2. Automation as irrigation**
Set up the system once & it runs continuously. Docker builds, tests, validation.
No manual watering. The system waters itself.
**3. Quality seeds = quality harvest**
First 3 implementations took careful work. Every subsequent implementation inherited that quality.
Invest in seed stock. Harvest scales automatically.
**4. Version control the genetics**
Prompts are genetic code. Version controlled, A/B tested & iterated daily.
Prompt engineering is genetic engineering.
**5. Solo operator, ecosystem leverage**
One person. One permacomputer. 57 implementations in 5 days.
Not through heroic effort. Through ecosystem design.
the harvest
===========
- 454 pages
- 57 tested implementations
- Complete Docker configs
- Public domain code
- $42, includes free uncloseai.com API access
More importantly: proved permacomputer can grow technical reference material at scale.
the evolution
=============
unturf. is a loose-knit collective of hackers disrupting wheels & fostering open collaboration.
We run `ai.unturf.com <https://ai.unturf.com/>`_ - free AI services.
We built `SLOP <https://slop.unturf.com/>`_ - Simple Language Open Protocol for AI.
We operate `git.unturf.com <https://git.unturf.com/>`_ - public domain code repositories.
We're growing Remarkbox, MakePostSell & now uncloseai as permacomputer crops.
This isn't a company. It's an ecosystem. Software permaculture.
The same patterns that grew this book in 5 days grow everything:
- API documentation
- Code example libraries
- Multi-language SDKs
- Tutorial content
- Technical training materials
Plant seeds, build automation, let ML propagate & harvest continuously.
Traditional publishing: manual labor at typing speed.
Permacomputer publishing: automated cultivation at validation pipeline speed.
Not one person writing code.
A collective cultivating an ecosystem.
Disrupting wheels. Fostering open collaboration. Making AI accessible.
The book grew in 5 days because we planted the right seeds in the right soil with the right automation & cultivation pipeline.
Permacomputer agriculture.
Join us: `unturf. <https://www.unturf.com/>`_
Grab the harvest: `uncloseai reference manual <https://shop.unturf.com/p/8486f492-a93e-11f0-b477-02dfe05770ee/uncloseai-machine-learning-reference-guide-to-inference-clients>`_
.. contents::