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
Have you asked Claude to critique this code? It's... not super complimentary. There are design anti-patterns I haven't seen in two decades.
It runs on plain LAMP without 400 node_modules to show a task list. The 2000s called, and their stack still boots faster than ours.
Look again.
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.
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.
Oh I thought it was to increase the chance of supply chain attacks and being caught in dependency hell.
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
why not just a notion template?
If Notion works for you, it’s a good choice. didn't for me.
Honestly, life OS doesn't work at all, in my opinion. The only thing that works is "quick and dirty" method
I'm attempting to do the same thing but for personal health Data.
Idea is solid. Execution.. leaves a lot to be desired.
Cool idea!
Thank you! Feedback welcome if you try it.
This is a neat idea!
Thanks!