blog shell

gistfile1.txt

**Shell of DN blog for [calculang](https://github.com/calculang/calculang)**

Under motivation I list:

- separation of concerns
- unity
- transparency
- democratisation of numbers

I need to elaborate on these, e.g. in relation to some examples.

I need to outline the must-know language principles/features:

- param inference & passing
- function/input/model/model-results uniformity
- modularity, recycling and models-of-models, e.g. relate to reconciliation/other patterns

For examples for blog purposes I need to work towards, at least:

- bounce and/or projectile
- maybe wedge for trig/forces stuff
- manufacturing model, demand curve, reconciliations/waterfall charts
- these can eventually lead to calculang for education posts (any level)
- [not abs. necessary for blog] simple climate model (e.g. A. kaya identity to project emissions, -> B. projection of d. carbon concentration and temperature change)
- [not abs. necessary for blog] simple neural network model

For audiences I need:

- git/hub for actuaries
- what does calculang offer developers/apps?
- data science & 'viz models not data'
- separation of concerns and specialties
- "declarative work"
- "reasonable" and reasoning
- something about functional programming
- for gaming an example/POC model using events

On specific developments:

- model explorer viz/interaction
- maybe hierarchy/granularity (or drilldown) work
- extensions work (browser, vscode)

For environments/cloud I need to discuss:

- github-repl-repo
- netlify/lambda fns, API hosting
- openness as a principle

I can write about some platforms and integrations, e.g.:

- ObservableHQ, remote/local
- vega/lite
- Idyll
- something no-code and this area
- platform-neutral as a principle

- interactivity "vs" auditability can tie above 2 lists together (auditability needs specific posts too)
- somewhere: not reinventing the wheel, using/use best-in-class tooling instead, starting with editor, environments (from dev-world)

For opening up use-cases I have:

- smart contracts: (sometimes?) not lawyers, now modellers? +transparency needs
- integration and co-ordination of systems (e.g., AI, or a more realistic and less approachable existing climate model)
- scope isn't bounded: now up to people what calculang does
- AI/validation/analysis
- agent-based modelling

Probably something on implementations, and discussing limitations in existing implementation, current/initial emphasis about scaling conceptually.

Probably something on migrations, migration to calculang, incremental. "steady as she migrates"?

Maybe I need to justify current non-priorities:

- deviating from Javascript-syntax apparent quirks, within calculang-js implementation (because this deviates from the largest developer community ever and:)
- UI: I have high expectations for possibilities around generation of calculang models/code via user-friendly interfaces, but I think about this as effectively a separate project/s