Could we have "content type" protocols like doc://, sheet://, code:// or design:// and a governing body to define the standards of those protocols? Bring your own storage provider for each protocol, and control your data.
Should only your senior staff be allowed to deploy to production? And do you keep junior developers away from certain parts of the codebase? You're creating "team debt"!
A Dockerfile and some application code that sits in a git repo, is the purest form of digital value that you can get.
Logs are thrown into code, just like comments. Comments doesn't add much value, is subtle to the code. But logs can potentially add value, however it clutters the code a lot.
APIs can scale vertical SaaS or integrated operations at any company. Shipping APIs is no exception, and provides a bridge from digital to physical for many software vendors.
