jdzikowski

I agree. But isn't it somewhat similar to syncing data with iCloud/OneDrive/GoogleDrive? A convenience service that manages your sensitive data. Just replace sync with cage. It's leakable, but might be also more convenient and cheaper than agents in the cloud.

I think there might be also another possible way to handle the sensitive data issue. Maybe in the future instead of putting agent into the cloud sandboxes, we let agents work locally and put sensitive data into "cages" or "vaults" agents can't access.

We are close to inventing something like deep modules [1] for markdown and a whole methodology of managing docs abstraction and layers. And I'm somewhat serious. It's hard to manage one random, interconnected bag of (spaghetti) markdown. Abstract is the new interface.

1. https://softengbook.org/articles/deep-modules

When resources are scarce, you are forced to use them in a meaningful way. You learn to do only what matters most: what is right, minimal, essential. When you need to choose wisely when resources are scarce -- this is how you learn the taste.

Now that creation is cheap, the scarcity has moved to adoption. Things built without taste are less likely to be adopted, to survive. At least that is what I'd like to believe.

> The role of a software engineer is foremost about the ownership of software systems, and secondarily about modifying them or developing new ones.

Yes! That's sooo accurate. Tools you use change, the level of abstraction you operate changes, but the role remains.

I built a language and runtime that combines agentic calls/prompts with strict checks (running tests, compiling, git commit).

https://jaiph.org/

I then used it to build other tools -- a personal time tracker and a Wesnoth-like game (both not yet published). Basically, I maintain a Markdown file with a queue of tasks, and I run a Jaiph workflow in a loop that automatically picks up tasks one by one and develops them with no human intervention.