The purpose of node_modules is to reduce the surface of ancillary code which one must maintain.
This allows the maintainer to focus on business logic, delegating universal, undifferentiating concerns to projects that respect those concerns as their own raison d'etre.
Thus is all running software respected as central, and not peripheral, during its development. This raises the quality of the code—increasing functionality, and reducing defects.
I have found it really helpful to just give read only access to application databases for my agents and since they have the source code they get to learn and run regular http calls against the services. As long as the service itself is built local first with say a sync engine works like a charm
I use Notion too. Claude suggested a MCP in front of Notion with rules about how to update Notion pages, and another MCP for other actions over Tailscale.
33 comments
[ 11.4 ms ] story [ 127 ms ] threadThis allows the maintainer to focus on business logic, delegating universal, undifferentiating concerns to projects that respect those concerns as their own raison d'etre.
Thus is all running software respected as central, and not peripheral, during its development. This raises the quality of the code—increasing functionality, and reducing defects.
https://github.com/edrisranjbar/lifeos/blob/c45f326716c5d89f...
The attachment system runs a `CREATE TABLE` call every time it's included, as a simple example of why this is a big mess.
I have zero objection to a plain, no-JS LAMP PHP site. But that can be done cleanly.