russellballestrini/russell.ballestrini.net
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions

weave botoform deeper, add permacomputer growth cycle ending with unsandbox

Browse source
This commit is contained in:
russell@unturf.com 2026-02-27 17:58:59 -05:00
parent 789e908e50
commit 603adeb858
1 changed files with 7 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

8
content/2026-02-27-a-love-story-about-jason.rst
View file

@ -34,7 +34,7 @@ I started seeing curly braces when I closed my eyes.
:align: center
:width: 400px
So I did what any rational person would do. I `wrote a library </dealing-with-pagination-in-python/>`_. While growing `Botoform <https://botoform.readthedocs.io/en/latest/>`_ to `manage AWS VPCs </output-all-instance-identifiers-of-an-aws-vpc-to-json/>`_ & `wrangle Boto3 responses </boto3-get-main-route-table/>`_, I kept hitting nested JSON walls. I ripped ``nested_lookup()`` out of that work & published it to `PyPI <https://pypi.org/project/nested-lookup/>`_. Public domain. Now nobody has to type ``response["data"]["data"]["results"][0]["data"]`` ever again. You just say ``nested_lookup("data", response)`` & it hands you every match from every depth. That frustration became a `real tool <https://git.unturf.com/python/nested-lookup>`_ that strangers install with ``pip``.
So I did what any rational person would do. I grew `Botoform <https://botoform.readthedocs.io/en/latest/>`_ to manage AWS infrastructure with YAML templates & JSON outputs. YAML in, JSON out. `VPC inventories dumped to JSON </output-all-instance-identifiers-of-an-aws-vpc-to-json/>`_. `Boto3 responses wrangled </boto3-get-main-route-table/>`_ through enriched abstractions. Every AWS API returned nested JSON so deep I `wrote a library </dealing-with-pagination-in-python/>`_ just to survive it. I ripped ``nested_lookup()`` out of that Botoform work & published it to `PyPI <https://pypi.org/project/nested-lookup/>`_. Public domain. Now nobody has to type ``response["data"]["data"]["results"][0]["data"]`` ever again. You just say ``nested_lookup("data", response)`` & it hands you every match from every depth. That frustration became a `real tool <https://git.unturf.com/python/nested-lookup>`_ that strangers install with ``pip``.
Love makes you grow things.
@ -122,6 +122,12 @@ For a while.
|
Looking back, every phase of this love story fed a rapid growth cycle. Botoform taught me to wrangle JSON from AWS APIs. `nested-lookup <https://pypi.org/project/nested-lookup/>`_ taught me to navigate any depth. `webwords </webwords-is-a-minimal-viable-web-app-with-docker-in-as-many-languages-as-possible/>`_ proved JSON speaks `42 languages </webwords-reaches-42-languages-the-ultimate-programming-kata/>`_. `SLOP </introducing-slop/>`_ proved JSON API standards can stay simple. All of that learning, every frustration & every high, grew into `unsandbox <https://unsandbox.com/cli>`_. 42+ languages. 30+ shells. 11,571 lines of C. Free code execution for anyone. JSON payloads carrying code to containers & results back to terminals.
A `permacomputer <https://unturf.com/let-us-define-a-permacomputer>`_ growth cycle. Infrastructure that outlasts its growers. Code that outlasts its authors. Every library, every API, every format war composted into soil for something larger. JSON carried it all. Still does. Still will.
|
.. code-block:: json
{