> Provide create() and destroy() functions for all data structures.

Every data structure (almost) must have defaultValue() and errorValue() functions too.

I have been making notes for a decade now. I have moved through plain txt files, no extension (linux style) txt files, CherryTree, SimpleNotes, LogSeq, Notion, GitHub Pages, Obsidian and may be more.

I have moved through phases of putting notes in physical notebook and scanning. I have 10s of scanned notebooks.

I have taken digital notes via stylus, via wacom pen and tablet, Samsung notes (best note taking app with stylus), a bunch of linux apps (xournal, xournal++ etc) and more...

I have written notes in pure html.

I have written personal app for taking notes in browser and storing it in postgres.

There is nothing better than text + git. Markdown is second.

My current configuration is: text/markdown + git + vs code + (plain) obsidian + plantuml + mermaid + local-git-server/github/gitlab etc.

While I don't disagree with the sentiment, an important feature for me is being able to read/write/search notes on mobile.

The idea of using spreadsheets is very clear, data in tabular form and charts. If that is the requirement, most low-code platforms would suffice too.

But, then the expectations are not articulated and managed properly, and management being management, thinks that they can retire grumpy oldies who build complex app in favor of low-code apps.

> The “code” is the easy part.

This is an understatement. Main problems are versioning, collaborating, maintenance.

Coding is like writing a story with other authors, with each chapter inspired by /writing-prompt, and publishing the whole book with new ISBN for every typo.

If app-publishing is fast, {no|low}-code wins. The obvious caveat being, that it is not a full fledged system where you can build yet another no-code platform on top of it.