Another anecdote supporting 'get it on one page'
- but for task scheduling!
"I find convenient to have all jobs schedule in one single file, and it's more obvious to see relations in jobs scheduling if you have several jobs in sight at once."
https://t.co/v6zo3SR9zg
I now think having tables as 2D code literals is dicey (hard to keep it readable when col length can vary), but I think a nice middle ground could be having the text representation be like a 'sparse matrix' (one line per entry) and have a spreadsheet UI represent it graphically.
This weekend I built =GPT3(), a way to run GPT-3 prompts in Google Sheets.
It's incredible how tasks that are hard or impossible to do w/ regular formulas become trivial.
For example: sanitize data, write thank you cards, summarize product reviews, categorize feedback...
But to be honest, in 2021, here is what I care about:
1. Tables, particularly calculated columns.
2. Seeing the big picture: inputs, outputs. Delay the 'how' until I need it.
3. Programs as 'pure' data transforms, with auto-recalc of dependencies.
4. Storing sheets as text.
If you found this Twitter via 2018's "Benefits of 2D code layouts" post, here is another way to put that point:
When writing a large Python program, you'll probably divide it up into sections (files) based on how the units of code relate to each other.